[Info-vax] VMS x86-64 compilers

[Dan Cross]

In article <Tsv5N.93490$rdid.19724 at fx12.ams4>,
Mark Daniel  <mark.daniel at wasd.vsm.com.au> wrote:
>On 17/11/2023 06:57, Dan Cross wrote:
>> In article <tDu5N.98763$YBDd.93660 at fx09.ams4>,
>> Mark Daniel  <mark.daniel at wasd.vsm.com.au> wrote:
>>> On 17/11/2023 06:20, Dan Cross wrote:
>>> [snip]
>>>> Why is it doing that?  I'd imagine inline assembler would be the
>>>> most likely culprit, but I'm guessing there.  I wonder if you
>>>> can get the compiler to emit an assembler listing?
>>>
>>> Excellent suggestion but unfortunately no.  The compile must quit very
>>> early.  The object file has zero content precluding
>>> ANA/OBJECT/DISASSEMBLE and while CC/LIST/MACHINE seems to be working
>>> with this release the .LIS is similarly empty.
>> 
>> I'm mildly surprised by this: I'd imagine a compiler invocation
>> equivalent to `clang -S` on a Unix-y system would quite before
>> object generation; here, you just want to see what instructions
>> the compiler would generate without it actually trying to create
>> object code.  I wonder if `CC/LIST/MACHINE/NOOBJECT` will do it?
>
>As noted by Craig the notes state /MACHINE still unsupported (does 
>generate a very nicely presented source listing though :-)  And no 
>object file.

Aww shucks; that's a bummer.

>> You definitely ought to be able to get it to generate LLVM byte
>> code (which happens well before target instruction selection,
>> let alone object code generation) which may give some clues as
>> to what's going on.
>
>A little LLVM in the HELP CC and nothing in SYS$HELP:CC.RELEASE_NOTES
>
>CC /ARCHITECTURE
>options to pass along to the LLVM code generator to select
>CC /OPTIMIZE
>options to pass along to the LLVM code generator to select

:-/ That's too bad.

	- Dan C.