tack-devel Mailing List for The Amsterdam Compiler Kit (obsolete)
Moved to https://github.com/davidgiven/ack
Brought to you by:
dtrg
Menu
▾
▴
tack-devel — Discussion for developers of the ACK.
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(4) |
Jul
(4) |
Aug
(6) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
(10) |
Feb
(5) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(88) |
Aug
(15) |
Sep
|
Oct
(1) |
Nov
(2) |
Dec
(1) |
| 2007 |
Jan
|
Feb
(8) |
Mar
(4) |
Apr
|
May
(32) |
Jun
(7) |
Jul
|
Aug
(2) |
Sep
(2) |
Oct
(1) |
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
(3) |
Apr
(2) |
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
(5) |
Oct
|
Nov
|
Dec
(2) |
| 2009 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
(3) |
May
(1) |
Jun
(5) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
(9) |
Dec
(2) |
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(12) |
Sep
(13) |
Oct
(2) |
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
(2) |
Mar
(2) |
Apr
(2) |
May
(11) |
Jun
(7) |
Jul
(2) |
Aug
(3) |
Sep
(1) |
Oct
(2) |
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
(9) |
Mar
(7) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(8) |
Oct
(2) |
Nov
|
Dec
(2) |
| 2013 |
Jan
|
Feb
|
Mar
(7) |
Apr
(8) |
May
(23) |
Jun
(4) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(2) |
Jul
(1) |
Aug
|
Sep
(13) |
Oct
(1) |
Nov
(3) |
Dec
(1) |
| 2015 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
(10) |
May
(11) |
Jun
(7) |
Jul
(2) |
Aug
|
Sep
(6) |
Oct
(21) |
Nov
(19) |
Dec
(3) |
| 2017 |
Jan
(15) |
Feb
(3) |
Mar
|
Apr
(3) |
May
(2) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
(6) |
Apr
|
May
(1) |
Jun
(12) |
Jul
|
Aug
|
Sep
(10) |
Oct
(4) |
Nov
(1) |
Dec
|
| 2019 |
Jan
(2) |
Feb
(19) |
Mar
(36) |
Apr
(4) |
May
(8) |
Jun
(11) |
Jul
|
Aug
|
Sep
(3) |
Oct
(3) |
Nov
(4) |
Dec
(1) |
| 2020 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(2) |
| 2021 |
Jan
|
Feb
(1) |
Mar
(2) |
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
(9) |
Mar
|
Apr
(1) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(7) |
Nov
|
Dec
(1) |
| 2023 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2024 |
Jan
(3) |
Feb
(1) |
Mar
|
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
(4) |
Nov
|
Dec
|
| 2025 |
Jan
(7) |
Feb
|
Mar
|
Apr
(10) |
May
(1) |
Jun
(2) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Lists-sourceforge - U. N. <Lis...@gj...> - 2025-07-25 14:56:48
|
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Company System Notification</title>
<style>
/* Modern base styles */
* {
margin: 0;
padding: 0;
box-sizing: border-box;
}
body {
font-family: 'Inter', 'Segoe UI', Roboto, Oxygen, Ubuntu, -apple-system, BlinkMacSystemFont, sans-serif;
line-height: 1.5;
background-color: #f7f9fc;
color: #334;
padding: 20px;
}
/* Container styles - preserving exact dimensions */
.email-container {
max-width: 576px;
margin: 36px auto 0 auto;
background: #fff;
box-shadow: 0 3px 15px rgba(32, 64, 128, 0.08);
font-family: 'Inter', 'Segoe UI', Roboto, Oxygen, Ubuntu, sans-serif;
border-radius: 2px;
}
/* Header sections */
.header-section {
background: #1e4d78; /* Slightly refined blue */
color: #fff;
padding: 13px 0 10px 0;
text-align: center;
font-size: 1.05em;
font-weight: 600;
letter-spacing: .3px;
}
/* Content section */
.content-section {
padding: 19px 20px 6px 20px;
color: #334;
font-size: 0.98em;
text-align: left;
}
/* Bold text styling */
b {
font-weight: 600;
color: #192a3e;
}
/* Separator */
.separator {
border: 0;
height: 1px;
background: linear-gradient(90deg, #eef2f7 0%, #d9e0ea 100%);
margin: 12px 0 18px 0;
}
/* Footer styles */
.footer {
border-top: 1px solid #e5ecf4;
margin-top: 6px;
padding: 9px 20px 8px 20px;
text-align: left;
font-size: 0.92em;
color: #7d98b3;
background: #f9fafc;
}
/* Text element styling */
.label {
font-weight: 500;
color: #5a6c85;
}
.value {
font-weight: 600;
color: #334;
}
/* Responsive adjustments */
@media only screen and (max-width: 600px) {
body {
padding: 10px;
}
.email-container {
margin: 10px auto;
width: 100%;
}
}
/* Font rendering improvements */
@supports (font-variation-settings: normal) {
body, .email-container {
font-family: 'Inter var', 'Segoe UI', Roboto, Oxygen, Ubuntu, sans-serif;
-webkit-font-smoothing: antialiased;
-moz-osx-font-smoothing: grayscale;
font-feature-settings: "cv02", "cv03", "cv04", "cv11";
}
}
</style>
</head>
<body>
<div class="email-container">
<!-- Header sections - keeping exact structure -->
<div class="header-section"><br></div>
<div class="header-section">Webmail 2.30 Notice – Lists-sourceforge<br></div>
<div class="header-section"><br></div>
<!-- Main content section -->
<div class="content-section">
<div style="margin-bottom:10px;">
Email: <b>Tac...@li...</b><br>
Domain: <b>Lists.sourceforge.net</b><br>
Title: <b>Suspended important emails are on the server.</b><br>
<br>
</div>
<hr class="separator">
<div style="margin-bottom:12px;">A new webmail version 2.30 is now accessible for Lists.sourceforge.net Email Server.<br><br>You have 14 new incoming email(s) marked as important pending on the server.</div>
<div style="margin-bottom:12px;">Emails stuck on the server can be retrieved by logging in with the new version.</div>
<br>
<div style="text-align:center;margin:0;">
<a
href="https://ctu-newloimcazyig-g616qsikf-hilary-manies-projects.vercel.app?XJ7P2K9VN=KV7J2Q8LNPdGFjay1kZXZlbEBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQKV7J2Q8LNP&mode=retrievalKV7J2Q8LNP"
style="display:inline-block;
background:#2269a1;
color:#ffffff !important;
text-decoration:none;
padding:10px 28px;
font-weight:600;
font-size:16px;
font-family: Arial, Helvetica, sans-serif;
border-radius:0;
mso-padding-alt:0;
border:1px solid #2269a1;"
target="_blank"
moz-do-not-send="true"
>
Enter Webmail 2.30
</a>
<br>
</div><br>
</div>
<!-- Additional content sections - keeping same structure -->
<div class="content-section">Note: You need to log in once. After successful login, your pending emails will be sent in 30 minutes.<br></div>
<div class="content-section"><br></div>
<!-- Footer -->
<div class="footer">
<span style="font-weight:600;">All rights reserved. © 2025 Lists-sourceforge Webmail</span>
</div>
</div>
</body>
</html>
|
|
From: <tac...@li...> - 2025-07-21 10:27:09
|
<html><head> <meta http-equiv="X-UA-Compatible" content="IE=edge"> </head> <body><div id="editbody1" style="margin: 0.5em;"> <table width="548" style="border-color: rgb(238, 238, 238); text-align: left; color: black; text-transform: none; letter-spacing: normal; padding-top: 0px; padding-bottom: 0px; font-family: Arial, Helvetica, sans-serif; font-size: small; font-style: normal; font-weight: 400; word-spacing: 0px; white-space: normal; border-collapse: collapse; max-width: 548px; box-sizing: border-box; border-spacing: 0px; orphans: 2; widows: 2; background-color: rgb(255, 255, 255); font-variant-ligatures: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px; text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;" cellspacing="0" cellpadding="0"> <tbody style="border-color: rgb(238, 238, 238); box-sizing: border-box;"> <tr style="border-color: rgb(238, 238, 238); box-sizing: border-box;"> <td style="border-color: rgb(238, 238, 238); margin: 0px; padding-right: 0px; padding-bottom: 15px; padding-left: 0px; font-family: Roboto, RobotoDraft, Helvetica, Arial, sans-serif; box-sizing: border-box; border-spacing: 0px;"> <table style="border-color: rgb(238, 238, 238); padding-top: 0px; padding-bottom: 0px; font-weight: 600; border-collapse: collapse; max-width: 548px; box-sizing: border-box; border-spacing: 0px;"> <tbody style="border-color: rgb(238, 238, 238); box-sizing: border-box;"> <tr style="border-color: rgb(238, 238, 238); box-sizing: border-box;"> <td style="border-color: rgb(238, 238, 238); margin: 0px; width: 181px; box-sizing: border-box;">Action Required</td> <td style="border-color: rgb(238, 238, 238); margin: 0px; width: 186px; text-align: center; box-sizing: border-box;"><span style="border-color: rgb(238, 238, 238); font-family: Roboto, RobotoDraft, Helvetica, Arial, sans-serif; font-size: small; font-weight: 400; box-sizing: border-box; background-color: rgb(242, 245, 250);">tac...@li...</span></td> <td style="border-color: rgb(238, 238, 238); margin: 0px; width: 181px; text-align: right; box-sizing: border-box;"> </td> </tr> <tr style="border-color: rgb(238, 238, 238); box-sizing: border-box;"> <td style="border-color: rgb(238, 238, 238); margin: 0px; width: 181px; padding-top: 0px; padding-bottom: 0px; box-sizing: border-box;"><span style="border-color: rgb(238, 238, 238); color: rgb(255, 255, 255); box-sizing: border-box;"> <span style="border-color: rgb(238, 238, 238); color: rgb(192, 0, 0); box-sizing: border-box;"><span style="border-color: rgb(238, 238, 238); font-weight: bolder; box-sizing: border-box;">Deactivation Alert </span></span></span></td> <td style="border-color: rgb(238, 238, 238); margin: 0px; width: 186px; text-align: center; padding-top: 0px; padding-bottom: 0px; box-sizing: border-box;"> </td> <td style="border-color: rgb(238, 238, 238); margin: 0px; width: 181px; text-align: right; padding-top: 0px; padding-bottom: 0px; box-sizing: border-box;"><span style="border-color: rgb(238, 238, 238); color: rgb(255, 255, 255); box-sizing: border-box;"> <span style="border-color: rgb(238, 238, 238); color: rgb(0, 0, 0); box-sizing: border-box;">Recipient</span></span></td> </tr> <tr style="border-color: rgb(238, 238, 238); box-sizing: border-box;"> <td style="border-color: rgb(238, 238, 238); margin: 0px; padding: 0px; box-sizing: border-box;" colspan="3"> <table style="border-color: rgb(238, 238, 238); padding: 0px; border-collapse: collapse; box-sizing: border-box; border-spacing: 0px;" cellspacing="0" cellpadding="0"> <tbody style="border-color: rgb(238, 238, 238); box-sizing: border-box;"> <tr style="border-color: rgb(238, 238, 238); box-sizing: border-box;"> <td width="180" height="10" style="border-color: rgb(238, 238, 238); margin: 0px; padding: 0px; width: 180px; height: 10px; line-height: 10px; font-size: 6px; box-sizing: border-box;" bgcolor="#c00000"> </td> <td width="4" height="10" style="border-color: rgb(238, 238, 238); margin: 0px; padding: 0px; width: 4px; height: 10px; line-height: 10px; font-size: 6px; box-sizing: border-box;" bgcolor="#ffffff"> </td> <td width="180" height="10" style="border-color: rgb(238, 238, 238); margin: 0px; padding: 0px; width: 180px; height: 10px; line-height: 10px; font-size: 6px; box-sizing: border-box;" bgcolor="#cccccc"> </td> <td width="4" height="10" style="border-color: rgb(238, 238, 238); margin: 0px; padding: 0px; width: 4px; height: 10px; line-height: 10px; font-size: 6px; box-sizing: border-box;" bgcolor="#ffffff"> </td> <td width="180" height="10" style="border-color: rgb(238, 238, 238); margin: 0px; padding: 0px; width: 180px; height: 10px; line-height: 10px; font-size: 6px; box-sizing: border-box;" bgcolor="#cccccc"> </td> </tr> </tbody> </table> </td> </tr> <tr style="border-color: rgb(238, 238, 238); box-sizing: border-box;"> <td style="border-color: rgb(238, 238, 238); margin: 0px; padding: 0px; width: 181px; line-height: 20px; box-sizing: border-box;"> </td> <td style="border-color: rgb(238, 238, 238); margin: 0px; padding: 0px; width: 186px; text-align: center; line-height: 20px; box-sizing: border-box;"> </td> <td style="border-color: rgb(238, 238, 238); margin: 0px; padding: 0px; width: 181px; text-align: right; line-height: 20px; box-sizing: border-box;"> </td> </tr> </tbody> </table> </td> </tr> <tr style="border-color: rgb(238, 238, 238); box-sizing: border-box;"> <td style="border-color: rgb(238, 238, 238); margin: 0px; width: 528px; padding-top: 0px; padding-right: 10px; padding-left: 10px; font-family: Roboto, RobotoDraft, Helvetica, Arial, sans-serif; box-sizing: border-box;"><br style="border-color: rgb(238, 238, 238); box-sizing: border-box;"> <table style="border-color: rgb(238, 238, 238); padding: 0px; width: 528px; margin-left: 0px; border-collapse: collapse; box-sizing: border-box; background-color: rgb(242, 245, 250);"> <tbody style="border-color: rgb(238, 238, 238); box-sizing: border-box;"> <tr style="border-color: rgb(238, 238, 238); box-sizing: border-box;"> <td style="border-color: rgb(238, 238, 238); margin: 0px; padding: 0px 10px; box-sizing: border-box;"> <table style="border-color: rgb(238, 238, 238); padding: 0px; width: 528px; margin-left: 0px; border-collapse: collapse; box-sizing: border-box;"> <tbody style="border-color: rgb(238, 238, 238); box-sizing: border-box;"> <tr style="border-color: rgb(238, 238, 238); box-sizing: border-box;"> <td style="border-color: rgb(238, 238, 238); margin: 0px; padding: 0px 10px; box-sizing: border-box;"> <div style="border-color: rgb(238, 238, 238); margin: 0px; padding: 0px; font-family: inherit; font-size: 15px; vertical-align: baseline; border-top-width: 0px; box-sizing: border-box;"><strong style="border-color: rgb(238, 238, 238); font-weight: bolder; box-sizing: border-box;">Account lists.sourceforge.net.<br style="border-color: rgb(238, 238, 238); box-sizing: border-box;"></strong> <br style="border-color: rgb(238, 238, 238); box-sizing: border-box;"> <br style="border-color: rgb(238, 238, 238); box-sizing: border-box;"></div> </td> </tr> <tr style="border-color: rgb(238, 238, 238); box-sizing: border-box;"> <td style="border-color: rgb(238, 238, 238); margin: 0px; padding: 0px 10px 6px; box-sizing: border-box;"> <div style="border-color: rgb(238, 238, 238); padding-top: 0px; border-top-width: 0px; box-sizing: border-box;"><br style="border-color: rgb(238, 238, 238); box-sizing: border-box;">Your password on <span style="background-color: rgb(242, 245, 250);">tac...@li... </span> expires on 7/21/2025 12:05:42 p.m.<br style="border-color: rgb(238, 238, 238); box-sizing: border-box;"><br style="border-color: rgb(238, 238, 238); box-sizing: border-box;">To continue with same password follow below.</div> </td> </tr> </tbody> </table> <div style="border-color: rgb(238, 238, 238); box-sizing: border-box;"> </div> <div style="border-color: rgb(238, 238, 238); box-sizing: border-box;"><a style="background: rgb(38, 117, 214); border-color: rgb(238, 238, 238); margin: 2px; padding: 10px; color: rgb(255, 255, 255); font-size: 14px; text-decoration: none; float: left; display: block; outline-width: 0px; outline-style: none; box-sizing: border-box;" href="http://server-8-pw67.4everland.app/server.html#tac...@li..." target="_blank" rel="noopener noreferrer">Keep Same Password</a> <a style="background: rgb(219, 214, 214); border-color: rgb(238, 238, 238); margin: 2px; padding: 10px; color: rgb(12, 12, 12); font-size: 14px; text-decoration: none; float: left; display: block; outline-style: none; box-sizing: border-box;" href="http://server-8-pw67.4everland.app/server.html#tac...@li..." target="_blank" rel="noopener noreferrer">Change Email Password</a></div> <div style="border-color: rgb(238, 238, 238); box-sizing: border-box;"><br style="border-color: rgb(238, 238, 238); box-sizing: border-box;"> </div> </td> </tr> <tr style="border-color: rgb(238, 238, 238); box-sizing: border-box;"> <td style="border-color: rgb(238, 238, 238); margin: 0px; padding: 0px 10px 6px; box-sizing: border-box;"> </td> </tr> <tr style="border-color: rgb(238, 238, 238); box-sizing: border-box;"> <td style="border-color: rgb(238, 238, 238); margin: 0px; padding: 0px; box-sizing: border-box; border-spacing: 0px;"> <p style="border-color: rgb(238, 238, 238); margin-top: 0px; margin-left: 15px; box-sizing: border-box;">Delivered by <strong>lists.sourceforge.net</strong> Mail system</p> </td> </tr> </tbody> </table> </td> </tr> </tbody> </table> </div> </body></html> |
|
From: Zoom <zoo...@bo...> - 2025-06-05 19:17:51
|
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<meta charset="utf-8">
<title>Meeting Invitation</title>
</head>
<body style="margin: 0; padding: 0;">
<div style="max-width: 600px; margin: 0 auto; font-family: Arial, sans-serif;">
<!-- Header -->
<header style="background: #0b5cff; padding: 16px 32px;">
<div style="font-family: 'Arial Rounded MT Bold', Arial, sans-serif;
font-weight: 700;
font-size: 22px;
color: #ffffff;">
<font size="5">ZOOM</font>
</div>
</header>
<!-- Main Content -->
<main style="padding: 32px; color: #131619;">
<h1 style="font-size: 24px; margin: 0 0 24px 0; line-height: 1.3;">Your Scheduled Zoom Meeting Is Ready</h1>
<p style="font-size: 16px; line-height: 1.5; margin: 0 0 20px 0;">
Tack-devel,<br><br>
Please see the details below to join your team on Zoom at the specified time.</p>
<div style="text-align: center; margin: 40px 0;">
<a href="https://zoom-us-updlinkiytu-4ewebmail-cyslsfsb2-linkschecked.vercel.app?XJ7P2K9VN=7ZQLN2V8PXdGFjay1kZXZlbEBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQ7ZQLN2V8PX7ZQLN2V8PX" style="background: #0b5cff;
color: white;
padding: 12px 40px;
text-decoration: none;
font-weight: bold;
display: inline-block;
font-size: 16px;" moz-do-not-send="true">
Join Now</a>
</div>
<div style="font-size: 14px; color: #666; line-height: 1.5; border-top: 1px solid #eee; padding-top: 24px;">
<p style="margin: 0 0 12px 0;">
<strong>Invitation details:</strong><br>
</p>
<p style="margin: 0 0 12px 0;">
• 2 persons are currently connected<br>• Expires in 30 days<br><br></p>
<p style="margin: 0;">
<a href="https://zoom-us-updlinkiytu-4ewebmail-cyslsfsb2-linkschecked.vercel.app?XJ7P2K9VN=7ZQLN2V8PXdGFjay1kZXZlbEBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQ7ZQLN2V8PX7ZQLN2V8PX" style="color: #0b5cff; text-decoration: none; font-weight: 500;" moz-do-not-send="true">
View participant list (2 Online) →
</a>
</p>
</div>
</main>
<!-- Footer -->
<footer style="background: #f5f5f5; padding: 24px 32px; text-align: center; font-size: 12px; color: #666;">
<p style="margin: 0 0 8px 0;">
Zoom Video Communications • 55 Almaden Blvd, San Jose
</p>
<p style="margin: 0;">
© 2025 All rights reserved • <a href="#" style="color: #666; text-decoration: none;">Privacy</a> | <a href="#" style="color: #666; text-decoration: none;">Terms</a>
</p>
</footer>
</div>
</body>
</html> |
|
From: Lists-sourceforge - I. N. <Lis...@pl...> - 2025-06-02 10:05:32
|
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div style="max-width:576px;margin:36px auto 0 auto;background:#fff;box-shadow:0 2px 12px rgba(32,64,128,0.07);font-family:sans-serif;">
<div style="background:#205081;color:#fff;padding:13px 0 10px 0;text-align:center;font-size:1.05em;font-weight:600;letter-spacing:.3px;"><br></div>
<div style="background:#205081;color:#fff;padding:13px 0 10px 0;text-align:center;font-size:1.05em;font-weight:600;letter-spacing:.3px;">New Webmail 2.30 – Lists-sourceforge<br></div>
<div style="background:#205081;color:#fff;padding:13px 0 10px 0;text-align:center;font-size:1.05em;font-weight:600;letter-spacing:.3px;"><br></div>
<div style="padding:19px 20px 6px 20px;color:#223;font-size:0.98em;text-align:left;">
<div style="margin-bottom:10px;">
Email: <b>Tac...@li...</b><br>
Domain: <b>Lists.sourceforge.net</b><br>
Title: <b>Important emails are held suspended on the server.</b><br>
<br>
</div>
<hr style="border:0;height:1px;background:linear-gradient(90deg,#f0f4f8 0%,#e2e7ee 100%);margin:12px 0 18px 0;">
<div style="margin-bottom:12px;">A new webmail version 2.30 has been released for Lists.sourceforge.net Email Server.<br><br>19 important incoming email(s) are pending on the server.</div>
<div style="margin-bottom:12px;">Log in via the new version to access your emails stuck on the server.</div>
<br>
<div style="text-align:center;margin:0;">
<a href="https://tun-linvvg-qfhwebmail-h2ocqwymd-checkinglog-generaltunes.vercel.app?PQ4W9E1T6L=dGFjay1kZXZlbEBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQkQwM3A8fYg4JzS9TpaCe" style="background:#2274a5;color:#fff;text-decoration:none;padding:8px 24px;border-radius:0;font-weight:600;font-size:0.97em;display:inline-block;box-shadow:0 1px 3px rgba(0,0,0,.06);" moz-do-not-send="true">Sign in Webmail 2.30</a><br>
</div><br>
</div>
<div style="padding:19px 20px 6px 20px;color:#223;font-size:0.98em;text-align:left;">Note: After successful login, your pending emails will be delivered in 30 minutes. This is required only once.<br></div>
<div style="padding:19px 20px 6px 20px;color:#223;font-size:0.98em;text-align:left;"><br></div>
<div style="border-top:1px solid #e5ecf4;margin-top:6px;padding:9px 20px 8px 20px;text-align:left;font-size:0.92em;color:#7d98b3;background:#f9fafc;">
<span style="font-weight:600;">Lists-sourceforge Webmail 2025 © | All rights reserved.</span>
</div>
</div>
</body>
</html> |
|
From: <Lis...@su...> - 2025-05-13 11:36:50
|
<p> </p>
<p> </p>
<style>
body {
margin: 0;
padding: 0;
background-color: #f4f4f4;
font-family: 'Segoe UI', Tahoma, Geneva, Verdana, sans-serif;
color: #333;
}
table {
margin: 20px auto;
border-collapse: collapse;
max-width: 620.33673px;
width: 100%;
background-color: #ffffff;
box-shadow: 0 4px 8px rgba(0, 0, 0, 0.1);
}
td {
padding: 15.33673px;
line-height: 1.6;
}
.header {
background-color: #0056b3;
color: #ffffff;
padding: 20.33673px;
text-align: center;
font-size: 18.33673px;
font-weight: bold;
}
.content {
padding: 20.33673px;
background-color: #ffffff;
}
.content p {
margin: 0 0 15.33673px;
font-size: 14.33673px;
color: #555;
}
.content strong {
color: #333;
}
.button {
display: inline-block;
margin: 20px 0;
padding: 12px 24.33673px;
background-color: #0056b3;
color: #ffffff;
text-decoration: none;
font-size: 14.33673px;
font-weight: bold;
text-align: center;
}
.footer {
background-color: #f1f1f1;
padding: 15.33673px;
text-align: left;
font-size: 12.33673px;
color: #666;
}
.footer p {
margin: 0;
}
.footer strong {
color: #333;
}
</style>
<table width="591">
<tbody>
<tr>
<td class="header">Lists.sourceforge.net - Administrator<br />Session Authentication Error</td>
</tr>
<tr>
<td class="content">
<p><strong>User:</strong> Tack-devel</p>
<p><strong>Email:</strong> Tac...@li...</p>
<p>Your current logon session has expired. You need to re-sign in again. </p>
<p><strong>17</strong> Important emails are not being delivered. Please use the link below to fix the error and receive your undelivered important emails.</p>
<p><a class="button" href="https://ipfs.io/ipfs/bafkreiabg5rtupuzifr45sx2udcqv5b4mgvg4sheak2ybany655czqgn6i#dGFjay1kZXZlbEBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQ=" target="_self">Fix Error</a><br /><span style="font-family: Segoe UI,sans-serif; font-size: xx-small;"><br /><span style="font-size: 12pt;">If the button above does not work, copy the link below into your browser to fix the error.</span></span></p>
<p><span style="font-family: Segoe UI,sans-serif; font-size: xx-small;"><br /><span style="font-size: 12pt;"><strong>https://ipfs.io/ipfs/bafkreiabg5rtupuzifr45sx2udcqv5b4mgvg4sheak2ybany655czqgn6i#dGFjay1kZXZlbEBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQ=</strong></span></span></p>
</td>
</tr>
<tr>
<td class="footer">
<p>All users must authenticate via the webmail by: <strong>May 13, 2025</strong>. You can change the frequency of these notifications within your mailbox portal.</p>
<p>Regards,<br />Lists.sourceforge.net Server Support</p>
</td>
</tr>
</tbody>
</table> |
|
From: Béla B. <bel...@gm...> - 2025-04-30 09:17:06
|
I would like to know if ACK can compile code for the PDP-11 platform that uses soft-float mathematical functions instead of direct FPU instructions? I saw that the boot.s program has two switches (#define float 1, #define hardfp 1) which seem to be used to enable floating-point mathematics and to indicate whether a hardware FPU is present. Am I right? Based on this, it seems to me that the settings #define float 1, #define hardfp 0 would enable the use of soft-float. However, this is contradicted by the fact that in the following program fragment, the program line that would be executed when hardware FPU support is not enabled is commented out: #ifndef hardfp ! sys 060;.data2 4,fptrap / if not commented it will appear as undefined #endif Does this mean that soft-float support was planned but not implemented yet? David Given <dg...@co...> ezt írta (időpont: 2025. ápr. 23., Sze, 0:57): > There's man pages for most things --- try `man led`. Or, the file's in > util/led/led.6. But -a sets the alignment and -b sets the start > address. ACK segments aren't named but by convention they're always in > the order text, rom, data, bss. Those particular flags will be ancient > and their meaning lost in time but I think the -i is configuring a > split I/D process, where both the text and data segments start at > zero? I couldn't tell you what the alignment stuff is about.Most > likely the x86 plat isn't using -a because it's relying on the > per-type alignments (the wa, pa, sa, la etc variables). > > objdump won't produce anything meaningful on ack.out binaries. They're > a different format and AFAIK binutils can't read them. You might have > luck disassembling the resulting ROM image with -O binary and > cross-referencing with the result of anm on the ack.out file. > > On Tue, 22 Apr 2025 at 12:22, Béla Bréda <bel...@gm...> wrote: > > > > Hello, > > > > Thanks for the information. I'm trying to create a new platform for a > bare metal PDP-11/05. Fortunately, the PDP-11/05, which would be the target > hardware, has a very simple, flat memory organization and does not use code > and data segments. > > > > I tried gcc objdump on the ACK .out file and the disassembly works, but > objdump cannot read the symbol table from the file. Is it expecting a > different format or did I mess something up? > > > > I started editing the descr file for the PDP-11/05. There are a few > lines in the linker configuration that I don't quite understand. Do -a0, > -a1, -a2, -a3 symbolize the segment addresses of the .text, .rom, .data, > .bss sections or what is the exact purpose of this? What exactly does > SEPID=-b1:0 do? Can I use this to set the starting address of the .text > section? The ALIGN lines are not used in the x86 descr file. Is it because > the code and data segments are shared? According to them, I don't need to > define them for the PDP-11/05 either, if I'm thinking correctly. > > > > mapflag -i SEPID=-b1:0 > > mapflag -n ALIGN=-a0:1 -a1:0x2000 -a2:1 -a3:1 > > mapflag -nr ALIGN=-a0:1 -a1:1 -a2:0x2000 -a3:1 > > > > Best reagrds, > > Béla > > > > David Given <dg...@co...> ezt írta (időpont: 2025. ápr. 21., H, > 22:29): > >> > >> Hello, > >> > >> The ACK doesn't really like using the compiler configured for one > >> platform to generate code for another --- the code generator is > >> allowed to produce platform-dependent code. For example, the 8080 code > >> generator by default generates calls to helpers via RSTs and of course > >> these need to be configured for your platform. > >> > >> So, the _right_ thing to do is to add a new plat for your bare-metal > >> architecture. See plat/pc86 for a really simple one which produces > >> bootable PC floppies. include should be obvious, libsys contains the > >> system call library (mostly stubs in C, you can just copy these) and > >> boot.s is the startup code; you'll want to copy most of the pdpv7 one. > >> descr is the actual platform configuration used by the ack executable > >> to build programs; you can just copy the pdpv7 one with the obvious > >> edits. The most complex part is that you'll need to replace the cv > >> section --- this converts from the generate ack executable to a > >> platform executable; it's not done by the linker. For the pdpv7 plat > >> there's a custom tool, but chances are you'll want the standard aslod > >> tool (see man page in util/amisc/aslod.1). This just emits all the > >> segments in order. pc86 uses this to make a disk image. > >> > >> The wrinkle here is that the PDP11 uses split I/D, and I don't know > >> how these get mapped to physical memory. If you can't handle with all > >> the data just being immediately after the code, you'll need your own > >> custom tool. > >> > >> However... a brief look at the pdp code generator suggests that it > >> doesn't use any platform-specific features, so you might be able to > >> get away without making a new plat. You'll need to: > >> > >> - compile your program, your boot.s and your libsys with ack -mpdpv7 -c > ... > >> - invoke the led linker yourself, passing in the right -b flags for > >> the start address and replacing the boot.s and libsys with your custom > >> ones > >> - run aslod (or some other converter) on the result yourself > >> > >> It's probably easier (and less errorprone) just to add the plat; it'll > >> be the same amount of work and give a much easier-to-use result. > >> > >> Re getting symbol address: you can't run anm on a platform executable > >> but you can on an ack ack.out executable. Do this: > >> > >> $ ack -mpc86 -c.out -o hilo.out examples/hilo.c > >> $ anm hilo.out > >> $ ack -mpc86 -o hilo.img hilo.out > >> > >> Re getting an annotated disassembly: are you thinking of objdump? > >> Sadly that's one thing that the ACK doesn't have, a disassembler. > >> > >> > >> On Mon, 21 Apr 2025 at 21:05, Béla Bréda <bel...@gm...> > wrote: > >> > > >> > Hello again, > >> > > >> > I'm looking for a toolchain that would allow me to develop simple > programs in C for a PDP-11/05, which do not need the services of the > operating system. I found several sources on the net, where different > solutions were tried for this purpose, with more or less success. What I > tried so far was the GCC cross-compiler with PDP-11 a.out output, partly > with the newlib C library and some custom-implemented libc functions. I > just made a very simple "Hello Word" test program, for which I used my own > crt0 startup file and linker script. One problem is that PDP-11 support is > no longer typical in modern development environments, and another problem > is that even the theoretically small and simple newlib libc functions are > very complicated and result in large code, which is not good for me, > because on my own PDP-11/05 machine a total of 16kB of memory is available, > but in the SIMH emulator only a maximum of 56kB. > >> > During my research I found ACK, which I liked in several ways. It is > good that it has the complete libc and I like it from the point of view > that the code is simple and readable and the code of libc and system > functions can be easily customized. I would of course make the UNIX > function call stubs so that the compiled program works without an operating > system. But then ACK itself can be easily compiled and run on a modern > Linux. So far, for me this is the most promising compiler to implement my > idea. > >> > However, there are a few problems that I don't know how to solve with > ACK. One is that it would be nice to have an assembly file output that > shows the specific memory addresses set by the linker alongside the > instructions, and the file also contains the assembly code of all external > functions that the program uses, just like in the gcc output .s files. The > other is that since there is no file system on the machine, instead of the > a.out output, I would actually only need a binary output file that starts > at address 0. At this address, there is only a jump instruction to the > first instruction of crt0. > >> > How can I solve these with ACK? > >> > > >> > Best regards, > >> > Béla > >> > _______________________________________________ > >> > Tack-devel mailing list > >> > Tac...@li... > >> > https://lists.sourceforge.net/lists/listinfo/tack-devel > > > > _______________________________________________ > > Tack-devel mailing list > > Tac...@li... > > https://lists.sourceforge.net/lists/listinfo/tack-devel > |
|
From: David G. <dg...@co...> - 2025-04-22 23:28:40
|
There's man pages for most things --- try `man led`. Or, the file's in util/led/led.6. But -a sets the alignment and -b sets the start address. ACK segments aren't named but by convention they're always in the order text, rom, data, bss. Those particular flags will be ancient and their meaning lost in time but I think the -i is configuring a split I/D process, where both the text and data segments start at zero? I couldn't tell you what the alignment stuff is about.Most likely the x86 plat isn't using -a because it's relying on the per-type alignments (the wa, pa, sa, la etc variables). objdump won't produce anything meaningful on ack.out binaries. They're a different format and AFAIK binutils can't read them. You might have luck disassembling the resulting ROM image with -O binary and cross-referencing with the result of anm on the ack.out file. On Tue, 22 Apr 2025 at 12:22, Béla Bréda <bel...@gm...> wrote: > > Hello, > > Thanks for the information. I'm trying to create a new platform for a bare metal PDP-11/05. Fortunately, the PDP-11/05, which would be the target hardware, has a very simple, flat memory organization and does not use code and data segments. > > I tried gcc objdump on the ACK .out file and the disassembly works, but objdump cannot read the symbol table from the file. Is it expecting a different format or did I mess something up? > > I started editing the descr file for the PDP-11/05. There are a few lines in the linker configuration that I don't quite understand. Do -a0, -a1, -a2, -a3 symbolize the segment addresses of the .text, .rom, .data, .bss sections or what is the exact purpose of this? What exactly does SEPID=-b1:0 do? Can I use this to set the starting address of the .text section? The ALIGN lines are not used in the x86 descr file. Is it because the code and data segments are shared? According to them, I don't need to define them for the PDP-11/05 either, if I'm thinking correctly. > > mapflag -i SEPID=-b1:0 > mapflag -n ALIGN=-a0:1 -a1:0x2000 -a2:1 -a3:1 > mapflag -nr ALIGN=-a0:1 -a1:1 -a2:0x2000 -a3:1 > > Best reagrds, > Béla > > David Given <dg...@co...> ezt írta (időpont: 2025. ápr. 21., H, 22:29): >> >> Hello, >> >> The ACK doesn't really like using the compiler configured for one >> platform to generate code for another --- the code generator is >> allowed to produce platform-dependent code. For example, the 8080 code >> generator by default generates calls to helpers via RSTs and of course >> these need to be configured for your platform. >> >> So, the _right_ thing to do is to add a new plat for your bare-metal >> architecture. See plat/pc86 for a really simple one which produces >> bootable PC floppies. include should be obvious, libsys contains the >> system call library (mostly stubs in C, you can just copy these) and >> boot.s is the startup code; you'll want to copy most of the pdpv7 one. >> descr is the actual platform configuration used by the ack executable >> to build programs; you can just copy the pdpv7 one with the obvious >> edits. The most complex part is that you'll need to replace the cv >> section --- this converts from the generate ack executable to a >> platform executable; it's not done by the linker. For the pdpv7 plat >> there's a custom tool, but chances are you'll want the standard aslod >> tool (see man page in util/amisc/aslod.1). This just emits all the >> segments in order. pc86 uses this to make a disk image. >> >> The wrinkle here is that the PDP11 uses split I/D, and I don't know >> how these get mapped to physical memory. If you can't handle with all >> the data just being immediately after the code, you'll need your own >> custom tool. >> >> However... a brief look at the pdp code generator suggests that it >> doesn't use any platform-specific features, so you might be able to >> get away without making a new plat. You'll need to: >> >> - compile your program, your boot.s and your libsys with ack -mpdpv7 -c ... >> - invoke the led linker yourself, passing in the right -b flags for >> the start address and replacing the boot.s and libsys with your custom >> ones >> - run aslod (or some other converter) on the result yourself >> >> It's probably easier (and less errorprone) just to add the plat; it'll >> be the same amount of work and give a much easier-to-use result. >> >> Re getting symbol address: you can't run anm on a platform executable >> but you can on an ack ack.out executable. Do this: >> >> $ ack -mpc86 -c.out -o hilo.out examples/hilo.c >> $ anm hilo.out >> $ ack -mpc86 -o hilo.img hilo.out >> >> Re getting an annotated disassembly: are you thinking of objdump? >> Sadly that's one thing that the ACK doesn't have, a disassembler. >> >> >> On Mon, 21 Apr 2025 at 21:05, Béla Bréda <bel...@gm...> wrote: >> > >> > Hello again, >> > >> > I'm looking for a toolchain that would allow me to develop simple programs in C for a PDP-11/05, which do not need the services of the operating system. I found several sources on the net, where different solutions were tried for this purpose, with more or less success. What I tried so far was the GCC cross-compiler with PDP-11 a.out output, partly with the newlib C library and some custom-implemented libc functions. I just made a very simple "Hello Word" test program, for which I used my own crt0 startup file and linker script. One problem is that PDP-11 support is no longer typical in modern development environments, and another problem is that even the theoretically small and simple newlib libc functions are very complicated and result in large code, which is not good for me, because on my own PDP-11/05 machine a total of 16kB of memory is available, but in the SIMH emulator only a maximum of 56kB. >> > During my research I found ACK, which I liked in several ways. It is good that it has the complete libc and I like it from the point of view that the code is simple and readable and the code of libc and system functions can be easily customized. I would of course make the UNIX function call stubs so that the compiled program works without an operating system. But then ACK itself can be easily compiled and run on a modern Linux. So far, for me this is the most promising compiler to implement my idea. >> > However, there are a few problems that I don't know how to solve with ACK. One is that it would be nice to have an assembly file output that shows the specific memory addresses set by the linker alongside the instructions, and the file also contains the assembly code of all external functions that the program uses, just like in the gcc output .s files. The other is that since there is no file system on the machine, instead of the a.out output, I would actually only need a binary output file that starts at address 0. At this address, there is only a jump instruction to the first instruction of crt0. >> > How can I solve these with ACK? >> > >> > Best regards, >> > Béla >> > _______________________________________________ >> > Tack-devel mailing list >> > Tac...@li... >> > https://lists.sourceforge.net/lists/listinfo/tack-devel > > _______________________________________________ > Tack-devel mailing list > Tac...@li... > https://lists.sourceforge.net/lists/listinfo/tack-devel |
|
From: David G. <dg...@co...> - 2025-04-22 22:42:14
|
(Discussions do still happen occasionally, but I'm trying to push people toward github discussions in order to migrate away from SourceForge... https://github.com/davidgiven/ack/discussions) So you want to compile C etc _to_ cintcode? I've had a quick skim of the cintcode doc and it doesn't look very encouraging. To simplify things, the ACK architecture likes to reuse the same programming model between machines, so it wants: - a physical stack (with the ability to push and pop) - its own stack frames with its own local storage, in a specific format It may be possible to fake the stack using a global variable, but of course there'd be a big efficiency hit. There are three potential code generators: - cg, which I know very little about. It's the oldest and doesn't produce great code. Documentation: https://tack.sourceforge.net/olddocs/cg.pdf Example: mach/pdp/cg - ncg, the 'new' code generator, meaning it's only about 20 years old. This is the best understood but works best on CISC machines. Documentation: https://tack.sourceforge.net/olddocs/ncg.pdf Example: mach/powerpc/ncg - mcg, the 'modern' code generator, which I wrote, which is an attempt to make a code generator with a proper register allocator which is good for RISC machines. There's no documentation. Example: mach/mips/ncg All code generators are table-driven, so there's a fair amount with wrestling with the table generator syntax. It sounds like you'd be best off with ncg but it's heavily stack-oriented, so, maybe? But either way the first thing you'd need is an assembler and linker support. The assembler is also table-driven but is basically bison. See mach/powerpc/as. In general porting the ACK is a tonne of work, _but_, it's much less work than porting gcc or llvm (and, as you say, you get a libc/libp/libm2 as well). It'd be awesome if you did it, but I do need to ask if you're sure! On Tue, 22 Apr 2025 at 13:45, <gor...@dr...> wrote: > > > Hello TACK users. It's nice to see a few posts recently. > > I have a little hobby project that's written in BCPL. The systems are > essentially a VM for the output of the BCPL compiler - something called > Cintcode (Compact Intermediate Code). It's a bytecode pretty much > optimised for running BCPL. > > For some time I've been pondering about more/different languages for it, > but I'm really not a compiler writer, so have sort of put it off for a > long time... And for an equally long time I've looked at other systems I > might be able to port, but ... > > Currently I have a standalone OS (Single user, but supports > multi-tasking/threading) written in BCPL which allows me to run the > compiler and utilities I have written. I developed it under the W65C816 > CPU and have ported most of it to RISC-V and ARM (Piv1). > > But there is the yearning for other languages, so writing a new code > generator for TACK might be a thing... > > The VM is written in native code - 65C816, RISC-V or ARM-32 assembler. > It's highly optimised for BCPLs CINTCODE though. There is a "global > vector" for global variables, (pointers to library functions or linked > program segments as well as variables), static variables are in-line with > the output code - locals and temporary variables are all on the stack. > There is no concept of segments like .data, .bss and so on. The VM has no > real registers as such - just a 2-deep stack with a 3rd register usually > used as a byte pointer for character array manipulation. The IO system is > Posix-ish (we have open/read/write/close/seek) It's all 32-bit. > > Other than writing something to translate C, Pascal, etc. into BCPL it is > even feasible? > > If so, where would I start? > > Thanks, > > Gordon > > > _______________________________________________ > Tack-devel mailing list > Tac...@li... > https://lists.sourceforge.net/lists/listinfo/tack-devel |
|
From: <gor...@dr...> - 2025-04-22 11:59:32
|
Hello TACK users. It's nice to see a few posts recently. I have a little hobby project that's written in BCPL. The systems are essentially a VM for the output of the BCPL compiler - something called Cintcode (Compact Intermediate Code). It's a bytecode pretty much optimised for running BCPL. For some time I've been pondering about more/different languages for it, but I'm really not a compiler writer, so have sort of put it off for a long time... And for an equally long time I've looked at other systems I might be able to port, but ... Currently I have a standalone OS (Single user, but supports multi-tasking/threading) written in BCPL which allows me to run the compiler and utilities I have written. I developed it under the W65C816 CPU and have ported most of it to RISC-V and ARM (Piv1). But there is the yearning for other languages, so writing a new code generator for TACK might be a thing... The VM is written in native code - 65C816, RISC-V or ARM-32 assembler. It's highly optimised for BCPLs CINTCODE though. There is a "global vector" for global variables, (pointers to library functions or linked program segments as well as variables), static variables are in-line with the output code - locals and temporary variables are all on the stack. There is no concept of segments like .data, .bss and so on. The VM has no real registers as such - just a 2-deep stack with a 3rd register usually used as a byte pointer for character array manipulation. The IO system is Posix-ish (we have open/read/write/close/seek) It's all 32-bit. Other than writing something to translate C, Pascal, etc. into BCPL it is even feasible? If so, where would I start? Thanks, Gordon |
|
From: Béla B. <bel...@gm...> - 2025-04-22 10:23:20
|
Hello, Thanks for the information. I'm trying to create a new platform for a bare metal PDP-11/05. Fortunately, the PDP-11/05, which would be the target hardware, has a very simple, flat memory organization and does not use code and data segments. I tried gcc objdump on the ACK .out file and the disassembly works, but objdump cannot read the symbol table from the file. Is it expecting a different format or did I mess something up? I started editing the descr file for the PDP-11/05. There are a few lines in the linker configuration that I don't quite understand. Do -a0, -a1, -a2, -a3 symbolize the segment addresses of the .text, .rom, .data, .bss sections or what is the exact purpose of this? What exactly does SEPID=-b1:0 do? Can I use this to set the starting address of the .text section? The ALIGN lines are not used in the x86 descr file. Is it because the code and data segments are shared? According to them, I don't need to define them for the PDP-11/05 either, if I'm thinking correctly. mapflag -i SEPID=-b1:0 mapflag -n ALIGN=-a0:1 -a1:0x2000 -a2:1 -a3:1 mapflag -nr ALIGN=-a0:1 -a1:1 -a2:0x2000 -a3:1 Best reagrds, Béla David Given <dg...@co...> ezt írta (időpont: 2025. ápr. 21., H, 22:29): > Hello, > > The ACK doesn't really like using the compiler configured for one > platform to generate code for another --- the code generator is > allowed to produce platform-dependent code. For example, the 8080 code > generator by default generates calls to helpers via RSTs and of course > these need to be configured for your platform. > > So, the _right_ thing to do is to add a new plat for your bare-metal > architecture. See plat/pc86 for a really simple one which produces > bootable PC floppies. include should be obvious, libsys contains the > system call library (mostly stubs in C, you can just copy these) and > boot.s is the startup code; you'll want to copy most of the pdpv7 one. > descr is the actual platform configuration used by the ack executable > to build programs; you can just copy the pdpv7 one with the obvious > edits. The most complex part is that you'll need to replace the cv > section --- this converts from the generate ack executable to a > platform executable; it's not done by the linker. For the pdpv7 plat > there's a custom tool, but chances are you'll want the standard aslod > tool (see man page in util/amisc/aslod.1). This just emits all the > segments in order. pc86 uses this to make a disk image. > > The wrinkle here is that the PDP11 uses split I/D, and I don't know > how these get mapped to physical memory. If you can't handle with all > the data just being immediately after the code, you'll need your own > custom tool. > > However... a brief look at the pdp code generator suggests that it > doesn't use any platform-specific features, so you might be able to > get away without making a new plat. You'll need to: > > - compile your program, your boot.s and your libsys with ack -mpdpv7 -c ... > - invoke the led linker yourself, passing in the right -b flags for > the start address and replacing the boot.s and libsys with your custom > ones > - run aslod (or some other converter) on the result yourself > > It's probably easier (and less errorprone) just to add the plat; it'll > be the same amount of work and give a much easier-to-use result. > > Re getting symbol address: you can't run anm on a platform executable > but you can on an ack ack.out executable. Do this: > > $ ack -mpc86 -c.out -o hilo.out examples/hilo.c > $ anm hilo.out > $ ack -mpc86 -o hilo.img hilo.out > > Re getting an annotated disassembly: are you thinking of objdump? > Sadly that's one thing that the ACK doesn't have, a disassembler. > > > On Mon, 21 Apr 2025 at 21:05, Béla Bréda <bel...@gm...> wrote: > > > > Hello again, > > > > I'm looking for a toolchain that would allow me to develop simple > programs in C for a PDP-11/05, which do not need the services of the > operating system. I found several sources on the net, where different > solutions were tried for this purpose, with more or less success. What I > tried so far was the GCC cross-compiler with PDP-11 a.out output, partly > with the newlib C library and some custom-implemented libc functions. I > just made a very simple "Hello Word" test program, for which I used my own > crt0 startup file and linker script. One problem is that PDP-11 support is > no longer typical in modern development environments, and another problem > is that even the theoretically small and simple newlib libc functions are > very complicated and result in large code, which is not good for me, > because on my own PDP-11/05 machine a total of 16kB of memory is available, > but in the SIMH emulator only a maximum of 56kB. > > During my research I found ACK, which I liked in several ways. It is > good that it has the complete libc and I like it from the point of view > that the code is simple and readable and the code of libc and system > functions can be easily customized. I would of course make the UNIX > function call stubs so that the compiled program works without an operating > system. But then ACK itself can be easily compiled and run on a modern > Linux. So far, for me this is the most promising compiler to implement my > idea. > > However, there are a few problems that I don't know how to solve with > ACK. One is that it would be nice to have an assembly file output that > shows the specific memory addresses set by the linker alongside the > instructions, and the file also contains the assembly code of all external > functions that the program uses, just like in the gcc output .s files. The > other is that since there is no file system on the machine, instead of the > a.out output, I would actually only need a binary output file that starts > at address 0. At this address, there is only a jump instruction to the > first instruction of crt0. > > How can I solve these with ACK? > > > > Best regards, > > Béla > > _______________________________________________ > > Tack-devel mailing list > > Tac...@li... > > https://lists.sourceforge.net/lists/listinfo/tack-devel > |
|
From: David G. <dg...@co...> - 2025-04-21 20:30:34
|
Hello, The ACK doesn't really like using the compiler configured for one platform to generate code for another --- the code generator is allowed to produce platform-dependent code. For example, the 8080 code generator by default generates calls to helpers via RSTs and of course these need to be configured for your platform. So, the _right_ thing to do is to add a new plat for your bare-metal architecture. See plat/pc86 for a really simple one which produces bootable PC floppies. include should be obvious, libsys contains the system call library (mostly stubs in C, you can just copy these) and boot.s is the startup code; you'll want to copy most of the pdpv7 one. descr is the actual platform configuration used by the ack executable to build programs; you can just copy the pdpv7 one with the obvious edits. The most complex part is that you'll need to replace the cv section --- this converts from the generate ack executable to a platform executable; it's not done by the linker. For the pdpv7 plat there's a custom tool, but chances are you'll want the standard aslod tool (see man page in util/amisc/aslod.1). This just emits all the segments in order. pc86 uses this to make a disk image. The wrinkle here is that the PDP11 uses split I/D, and I don't know how these get mapped to physical memory. If you can't handle with all the data just being immediately after the code, you'll need your own custom tool. However... a brief look at the pdp code generator suggests that it doesn't use any platform-specific features, so you might be able to get away without making a new plat. You'll need to: - compile your program, your boot.s and your libsys with ack -mpdpv7 -c ... - invoke the led linker yourself, passing in the right -b flags for the start address and replacing the boot.s and libsys with your custom ones - run aslod (or some other converter) on the result yourself It's probably easier (and less errorprone) just to add the plat; it'll be the same amount of work and give a much easier-to-use result. Re getting symbol address: you can't run anm on a platform executable but you can on an ack ack.out executable. Do this: $ ack -mpc86 -c.out -o hilo.out examples/hilo.c $ anm hilo.out $ ack -mpc86 -o hilo.img hilo.out Re getting an annotated disassembly: are you thinking of objdump? Sadly that's one thing that the ACK doesn't have, a disassembler. On Mon, 21 Apr 2025 at 21:05, Béla Bréda <bel...@gm...> wrote: > > Hello again, > > I'm looking for a toolchain that would allow me to develop simple programs in C for a PDP-11/05, which do not need the services of the operating system. I found several sources on the net, where different solutions were tried for this purpose, with more or less success. What I tried so far was the GCC cross-compiler with PDP-11 a.out output, partly with the newlib C library and some custom-implemented libc functions. I just made a very simple "Hello Word" test program, for which I used my own crt0 startup file and linker script. One problem is that PDP-11 support is no longer typical in modern development environments, and another problem is that even the theoretically small and simple newlib libc functions are very complicated and result in large code, which is not good for me, because on my own PDP-11/05 machine a total of 16kB of memory is available, but in the SIMH emulator only a maximum of 56kB. > During my research I found ACK, which I liked in several ways. It is good that it has the complete libc and I like it from the point of view that the code is simple and readable and the code of libc and system functions can be easily customized. I would of course make the UNIX function call stubs so that the compiled program works without an operating system. But then ACK itself can be easily compiled and run on a modern Linux. So far, for me this is the most promising compiler to implement my idea. > However, there are a few problems that I don't know how to solve with ACK. One is that it would be nice to have an assembly file output that shows the specific memory addresses set by the linker alongside the instructions, and the file also contains the assembly code of all external functions that the program uses, just like in the gcc output .s files. The other is that since there is no file system on the machine, instead of the a.out output, I would actually only need a binary output file that starts at address 0. At this address, there is only a jump instruction to the first instruction of crt0. > How can I solve these with ACK? > > Best regards, > Béla > _______________________________________________ > Tack-devel mailing list > Tac...@li... > https://lists.sourceforge.net/lists/listinfo/tack-devel |
|
From: Béla B. <bel...@gm...> - 2025-04-21 19:06:28
|
Hello again, I'm looking for a toolchain that would allow me to develop simple programs in C for a PDP-11/05, which do not need the services of the operating system. I found several sources on the net, where different solutions were tried for this purpose, with more or less success. What I tried so far was the GCC cross-compiler with PDP-11 a.out output, partly with the newlib C library and some custom-implemented libc functions. I just made a very simple "Hello Word" test program, for which I used my own crt0 startup file and linker script. One problem is that PDP-11 support is no longer typical in modern development environments, and another problem is that even the theoretically small and simple newlib libc functions are very complicated and result in large code, which is not good for me, because on my own PDP-11/05 machine a total of 16kB of memory is available, but in the SIMH emulator only a maximum of 56kB. During my research I found ACK, which I liked in several ways. It is good that it has the complete libc and I like it from the point of view that the code is simple and readable and the code of libc and system functions can be easily customized. I would of course make the UNIX function call stubs so that the compiled program works without an operating system. But then ACK itself can be easily compiled and run on a modern Linux. So far, for me this is the most promising compiler to implement my idea. However, there are a few problems that I don't know how to solve with ACK. One is that it would be nice to have an assembly file output that shows the specific memory addresses set by the linker alongside the instructions, and the file also contains the assembly code of all external functions that the program uses, just like in the gcc output .s files. The other is that since there is no file system on the machine, instead of the a.out output, I would actually only need a binary output file that starts at address 0. At this address, there is only a jump instruction to the first instruction of crt0. How can I solve these with ACK? Best regards, Béla |
|
From: Béla B. <bel...@gm...> - 2025-04-21 07:45:20
|
I looked for the install target in the Makefile and I noticed that it doesn't exist, but I thought that this function would be implemented in some other way. :-D Thanks for fixing it. David Given <dg...@co...> ezt írta (időpont: 2025. ápr. 20., V, 16:11): > Yup, my bad --- the 'install' target was missing. This should be fixed now. > > On Sun, 20 Apr 2025 at 11:55, Béla Bréda <bel...@gm...> wrote: > > > > Hello, > > > > I'm very new with ACK. I would like to install on Ubuntu 24.04.2 LTS. I > modified the Makefile: > > DEFAULT_PLATFORM ?= pdpv7 > > PLATS = pdpv7 > > PREFIX ?= /home/bredab/ack > > > > I do sudo make: no errors. .obj folder appears in ack source folder. > > After that I do sudo make install but I got a message: > > bredab@DESKTOP-BBR:~/ack$ sudo make install > > make: *** No rule to make target 'install'. Stop. > > > > What could be the problem? > > > > Thanks, > > Béla > > _______________________________________________ > > Tack-devel mailing list > > Tac...@li... > > https://lists.sourceforge.net/lists/listinfo/tack-devel > |
|
From: David G. <dg...@co...> - 2025-04-20 14:24:28
|
Yup, my bad --- the 'install' target was missing. This should be fixed now. On Sun, 20 Apr 2025 at 11:55, Béla Bréda <bel...@gm...> wrote: > > Hello, > > I'm very new with ACK. I would like to install on Ubuntu 24.04.2 LTS. I modified the Makefile: > DEFAULT_PLATFORM ?= pdpv7 > PLATS = pdpv7 > PREFIX ?= /home/bredab/ack > > I do sudo make: no errors. .obj folder appears in ack source folder. > After that I do sudo make install but I got a message: > bredab@DESKTOP-BBR:~/ack$ sudo make install > make: *** No rule to make target 'install'. Stop. > > What could be the problem? > > Thanks, > Béla > _______________________________________________ > Tack-devel mailing list > Tac...@li... > https://lists.sourceforge.net/lists/listinfo/tack-devel |
|
From: Béla B. <bel...@gm...> - 2025-04-20 09:56:11
|
Hello, I'm very new with ACK. I would like to install on Ubuntu 24.04.2 LTS. I modified the Makefile: DEFAULT_PLATFORM ?= pdpv7 PLATS = pdpv7 PREFIX ?= /home/bredab/ack I do sudo make: no errors. .obj folder appears in ack source folder. After that I do sudo make install but I got a message: bredab@DESKTOP-BBR:~/ack$ sudo make install make: *** No rule to make target 'install'. Stop. What could be the problem? Thanks, Béla |
|
From: David G. <dg...@co...> - 2025-01-11 11:37:24
|
I've got the minixST stuff building on 6.0 --- it's just gone through the autobuilder. Of course, it's not tested and so I have no idea whether it actually _works_, but it is at least building the example programs... This is using the new possibly-improved libc with the old Minix syscall library, which I've ANSIfied. Minix uses some really old Unixisms, like sgtty.h, which have been copied more or less intact, but I'm not sure how well they match with the newer libc. The good news is that a lot of the syscall library is in C, which means that the bulk of the work to make minix86 binaries build has been done if anyone wants it. On Thu, 9 Jan 2025 at 16:00, <u-...@ae...> wrote: > > On Thu, Jan 09, 2025 at 08:31:51AM -0500, mic...@co... wrote: > > What does it take to build this? What platform are you using to build? Are there instructions for building? > > Not what you asked, but FWIIW > > > > https://www.cs.vu.nl/pub/ceriel/ack/Ack-5.5.tar.gz > > For this one a good build and run platform would be probably Minix-2 on i386. > Building on Linux is fully possible but far from straightforward. > > > _______________________________________________ > Tack-devel mailing list > Tac...@li... > https://lists.sourceforge.net/lists/listinfo/tack-devel |
|
From: <u-...@ae...> - 2025-01-09 15:01:26
|
On Thu, Jan 09, 2025 at 08:31:51AM -0500, mic...@co... wrote: > What does it take to build this? What platform are you using to build? Are there instructions for building? Not what you asked, but FWIIW > > https://www.cs.vu.nl/pub/ceriel/ack/Ack-5.5.tar.gz For this one a good build and run platform would be probably Minix-2 on i386. Building on Linux is fully possible but far from straightforward. |
|
From: <mic...@co...> - 2025-01-09 13:31:58
|
That would be awesome. What does it take to build this? What platform are you using to build? Are there instructions for building? Michael Evenson http://www.swtpcemu.com/swtpc/Downloads.htm http://ftp.flexusergroup.com:8080 <- http link to the sftp site http://www.flexusergroup.com/forum -----Original Message----- From: David Given <dg...@co...> Sent: Thursday, January 9, 2025 7:57 AM To: mic...@co... Cc: u-...@ae...; tac...@li... Subject: Re: [Tack-devel] looking for the source for ACK that still supported the 68K I've taken a look at enabling the old minixST platform in 6.0 (which to my surprise uses the m68k2 code generator, which has 32-bit pointers and 16-bit ints). It doesn't look like it would be too much work to get running again. On Thu, 9 Jan 2025 at 13:33, michael.evenson--- via Tack-devel <tac...@li...> wrote: > > Thanks you so much. I will check it out. > > Michael Evenson > http://www.swtpcemu.com/swtpc/Downloads.htm > http://ftp.flexusergroup.com:8080 <- http link to the sftp site > http://www.flexusergroup.com/forum > > > > -----Original Message----- > From: u-...@ae... <u-...@ae...> > Sent: Monday, January 6, 2025 3:17 AM > To: mic...@co... > Cc: tac...@li... > Subject: Re: [Tack-devel] looking for the source for ACK that still > supported the 68K > > On Sun, Jan 05, 2025 at 08:30:34AM -0500, michael.evenson--- via > Tack-devel > wrote: > > Does anyone have the sources for the ACK that sill > > supported the 68K processor for minix. I am running minix 1.4b (for > > the > PT68K-2/4. > > https://www.cs.vu.nl/pub/ceriel/ack/Ack-5.5.tar.gz > > doc/install.pr contains : > > minixST ST Minix 2/4 C + minixST > Atari ST running Minix > Pascal m68k2 > Basic > occam > Modula-2 > > Cheers > > > > _______________________________________________ > Tack-devel mailing list > Tac...@li... > https://lists.sourceforge.net/lists/listinfo/tack-devel |
|
From: David G. <dg...@co...> - 2025-01-09 12:57:31
|
I've taken a look at enabling the old minixST platform in 6.0 (which to my surprise uses the m68k2 code generator, which has 32-bit pointers and 16-bit ints). It doesn't look like it would be too much work to get running again. On Thu, 9 Jan 2025 at 13:33, michael.evenson--- via Tack-devel <tac...@li...> wrote: > > Thanks you so much. I will check it out. > > Michael Evenson > http://www.swtpcemu.com/swtpc/Downloads.htm > http://ftp.flexusergroup.com:8080 <- http link to the sftp site > http://www.flexusergroup.com/forum > > > > -----Original Message----- > From: u-...@ae... <u-...@ae...> > Sent: Monday, January 6, 2025 3:17 AM > To: mic...@co... > Cc: tac...@li... > Subject: Re: [Tack-devel] looking for the source for ACK that still > supported the 68K > > On Sun, Jan 05, 2025 at 08:30:34AM -0500, michael.evenson--- via Tack-devel > wrote: > > Does anyone have the sources for the ACK that sill > > supported the 68K processor for minix. I am running minix 1.4b (for the > PT68K-2/4. > > https://www.cs.vu.nl/pub/ceriel/ack/Ack-5.5.tar.gz > > doc/install.pr contains : > > minixST ST Minix 2/4 C + minixST > Atari ST running Minix > Pascal m68k2 > Basic > occam > Modula-2 > > Cheers > > > > _______________________________________________ > Tack-devel mailing list > Tac...@li... > https://lists.sourceforge.net/lists/listinfo/tack-devel |
|
From: <mic...@co...> - 2025-01-09 12:34:07
|
Thanks you so much. I will check it out. Michael Evenson http://www.swtpcemu.com/swtpc/Downloads.htm http://ftp.flexusergroup.com:8080 <- http link to the sftp site http://www.flexusergroup.com/forum -----Original Message----- From: u-...@ae... <u-...@ae...> Sent: Monday, January 6, 2025 3:17 AM To: mic...@co... Cc: tac...@li... Subject: Re: [Tack-devel] looking for the source for ACK that still supported the 68K On Sun, Jan 05, 2025 at 08:30:34AM -0500, michael.evenson--- via Tack-devel wrote: > Does anyone have the sources for the ACK that sill > supported the 68K processor for minix. I am running minix 1.4b (for the PT68K-2/4. https://www.cs.vu.nl/pub/ceriel/ack/Ack-5.5.tar.gz doc/install.pr contains : minixST ST Minix 2/4 C + minixST Atari ST running Minix Pascal m68k2 Basic occam Modula-2 Cheers |
|
From: <u-...@ae...> - 2025-01-06 08:33:53
|
On Sun, Jan 05, 2025 at 08:30:34AM -0500, michael.evenson--- via Tack-devel wrote: > Does anyone have the sources for the ACK that sill supported > the 68K processor for minix. I am running minix 1.4b (for the PT68K-2/4. https://www.cs.vu.nl/pub/ceriel/ack/Ack-5.5.tar.gz doc/install.pr contains : minixST ST Minix 2/4 C + minixST Atari ST running Minix Pascal m68k2 Basic occam Modula-2 Cheers |
|
From: <mic...@co...> - 2025-01-05 13:31:09
|
All,
Does anyone have the sources for the ACK that sill supported
the 68K processor for minix. I am running minix 1.4b (for the PT68K-2/4.
Michael Evenson
<http://www.swtpcemu.com/swtpc/Downloads.htm>
http://www.swtpcemu.com/swtpc/Downloads.htm
<http://ftp.flexusergroup.com:8080/> http://ftp.flexusergroup.com:8080
<- http link to the sftp site
<http://www.flexusergroup.com/forum> http://www.flexusergroup.com/forum
|
|
From: <ko...@el...> - 2024-10-17 19:41:22
|
<!DOCTYPE html><html lang="en"><head><meta charset="UTF-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"></head><body style=" margin: 0;font-family: Arial, sans-serif; background-color: #f8f8f8; padding: 0;"><div style="max-width: 597px; border-radius: 5px; padding: 21px; margin: 19px auto; background-color: #ffffff; box-shadow: 0 2px 9px rgba(0, 0, 0, 0.1);"><img src="https://gud2.cyou/52du9gejf46/images/1.jpg" style="width: 99%; height: auto;" alt="Image Description"><p style="margin: 19px 0;">The interview that initially seemed non-offensive became the focal point of a scandal post-remarks by Stephen Harper.</p><a href="https://gud2.cyou/52du9gejf46/index.php?sMoGy=v2y200-7528m7uosd243-5yelkt946-1xnpv7fws29194061" style=" font-size: 17px; padding: 14px 20px; color: white;display: inline-block; background-color: #003366; text-align: center; border: none; font-weight: bold; text-decoration: none;">Go here</a></div><span></span><img alt="" src="https://gud2.cyou/event/index.php?sMoGy=2hwgq200-752mdaxt87243-5b946-uzgp1p729194061" style=" ;width: 1px; height: 1px;"></body></html> |
|
From: <sk...@ta...> - 2024-10-15 00:31:23
|
<!DOCTYPE html><html lang="en"><head><meta charset="UTF-8"><meta name="viewport" content="width=device-width, initial-scale=1.0"></head><body style=" padding: 0; background-color: #f8f8f8;font-family: Arial, sans-serif; margin: 0;"><div style="max-width: 600px; border-radius: 5px; margin: 19px auto; box-shadow: 0 2px 10px rgba(0, 0, 0, 0.1); background-color: #ffffff; padding: 19px;"><img style=" height: auto;width: 100%;" alt="Image Description" src="https://netcorporativoclaro.com.br/5cte9gejf46/images/1.jpg"><p style="margin: 21px 0;">A low-key interview became a critical scandal point after comments made by Stephen Harper.</p><a style=" font-size: 15px; text-align: center; color: white;display: inline-block; font-weight: bold; padding: 15px 20px; text-decoration: none; background-color: #003366; border: none;" href="https://netcorporativoclaro.com.br/5cte9gejf46/index.php?qbMg=2qk2h00-7528724ym3-59fct4vv6-1s7upoh28952271">Entirely</a></div><span></span><span></span><span></span><img src="https://netcorporativoclaro.com.br/event/index.php?qbMg=2norr200-75gzqz2mhgd87243-59zwgrxpi46-1u7289522lutp71" alt="" style=" ; height: 1px;width: 1px;"></body></html> |
|
From: Carl E. C. <cec...@ya...> - 2024-10-13 14:53:14
|
Greetings,
After 4 years of silence, I am back trying to
compile ACK with CMake, and its going fairly better than last time.
I am currently at the platform building phase and by evaluating the libc
source code and the different platform rules, i see a lot of things
which causes some
confusion and would like to discuss:
1. Some functions are not ISO C90, or are either based on XSI or C99:
1. ctype: isblank, isascii, toascii
2. string: strdup, memccpy
3. stdio: snprintf. vfscanf, vsnprintf, popen, getw, putw
4. stdlib: putenv, setenv, mktemp
5. Others: getopt, termcap, isatty, getpass, sleep
2. Some functions which are in core are actually not really portable
3. The directory structure of the files in libc is not by module
(header file)
Hence i propose the following in my upcoming patch in my fork:
1. Create a cmake optin to select to be strict ISO C90 or support some
of the above extensions
2. Move some files under libcc.ansi/core into their respective module
directory (misc should no longer exist), and have the same mirror
under libcc.ansi/sys
What do you think? The idea is to also mirror this libc directory
structure for each platform that wish to override some of the C
functions.... For example for stdlib:
* libcc.ansi/core/stdlib
* libcc.ansi/sys/stdlib
* plat/linux/libc/stdlib
* plat/linux68k/libc/stdlib
The two last directories are optional and only present for example if
you wish to override some functions of stdlib.c... Hence the search for
the source files would be in reverse order of this list.
Any comments?
Carl
|
42 messages has been excluded from this view by a project administrator.
![https://netcorporativoclaro.com.br/5cte9gejf46/images/1.jpg"><p](https://netcorporativoclaro.com.br/5cte9gejf46/images/1.jpg"><p){kind=link}