On 04/24/2024 16:57, finxx wrote:
> > People still are using it, and here's one relatively recent discussion of relevance, where particularly the lab equipment argument is one that often gets overlooked:
> 
> I can understand if people can't upgrade, but I don't think that a modern peice
> of software should be required to accomodate for them. It is fine if you want
> to implement it, I just don't think it would be worth it.
> 
> > Windows could mean in this context either win32 (utf-16) or midipix (int); and even without the midipix target, to properly implement L' literals from within QBE you'd need to make the size of wchar_t a target-specific property.
> 
> This should be a job for the language front-end, not QBE.
> 

It is possible for the language front-end to take care of that, of course, but then the generated qbe will be in the form of an array, not a string literal.

On 04/24/2024 14:29, finxx wrote:
> The naming is pretty messy; I just wrote the first thing that came to mind.
> I want to keep the target name short, though. amd64_windows is a bit too
> long in my opinion. amd64_win32 is a bit misleading, as it makes you wonder
> if it really is 64-bit or not. I also feel like calling the "midipix" target
> "winnt" is REALLY misleading.
> 

Re. amd64_win32 -- I believe that would be in line with x86_64-w64-mingw32, which is one of the binutils/gcc win64 target names. Then again, one has to keep in mind that Win32 predominantly refers to the application api (as opposed to the target abi), as explained for instance here:

- https://learn.microsoft.com/en-us/windows/win32/desktop-programming

> 32-bit support doesn't seem to be a priority. I for one think it should die
> already.

Greetings,

This is very exciting! One nit, though: the target and abi suffixes and identifiers are somewhat inconsistent due to an alternation between win, winabi, and windows. To that end, how about the following:

- _winabi for the (framework-independent) ABI.
- _win32 for cygwin/msys2 targets.
_ _winnt for the midipix target.


Rationale:

- _winbi should implement the x86 software conventions as described in https://learn.microsoft.com/en-us/cpp/build/x64-software-conventions

- _win32 should implement all bits pertaining to the cygwin/msys2 target variant, specifically with respect to long (LP64), wchar_t (short), and _start, main(), and related matters.