public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Simon Richter <Simon.Richter@hogyros.de>
To: binutils@sourceware.org
Subject: Re: Elimination of all floating point code in the tiny assembler
Date: Thu, 14 Sep 2023 17:38:39 +0900	[thread overview]
Message-ID: <5472869a-ca19-f267-8b08-46d2e07c527c@hogyros.de> (raw)
In-Reply-To: <6EBBE0A0-48BA-4C4D-8552-E1151D2DB681@jacob.remcomp.fr>

Hi,

On 9/14/23 16:49, jacob navia wrote:

> Big endian hosts have disappeared long ago.

In the hobbyist market, yes. POWER and zSeries still exist, and are in 
active use.

> Doing cross assembly in a 32 bit host for a 64 bit host… that looks weird but maybe possible, even if I would say that doing cross assembly in a 64 bit host for a 32 bit target would be more easy to find.

Both are fairly normal, and I'd argue that the ability to bootstrap a 64 
bit system from a 32 bit system is quite important.

This is also a matter of code quality. Baking assumptions into the code 
leads to maintainability issues down the line as someone will have to 
identify the problem and manually trace it back to the spot in the code 
where the assumption was made that doesn't quite hold.

> I have created a framework where you CAN do changes in a relatively tiny piece of software and see all effects immediately. Just download the tiny assembler and you are all set. You have a small 35 000 lines asm.c and a 10 000 lines asm.h. Period. Nothing else. And compiles everywhere since it is standard C.

But does it work everywhere, or does it silently fail in a way that it 
generates broken data, causing other people to spend significant amounts 
of time finding out what the problem is, report it and be told that 
their use case is out of scope? Because we have way too many "free 
software" projects like that.

    Simon

  parent reply	other threads:[~2023-09-14  8:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-10 17:41 jacob navia
2023-09-13 11:18 ` Nick Clifton
2023-09-13 13:54   ` Christian Groessler
2023-09-13 14:01     ` Paul Koning
2023-09-14  7:49   ` jacob navia
2023-09-14  8:35     ` Jan Beulich
2023-09-14 11:10       ` jacob navia
2023-09-14  8:38     ` Simon Richter [this message]
2023-09-14 13:48       ` Paul Koning

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5472869a-ca19-f267-8b08-46d2e07c527c@hogyros.de \
    --to=simon.richter@hogyros.de \
    --cc=binutils@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).