MACRO32 CONCODEXP messasge

OpenVMS x86 native compilers, cross compilers news and questions.
Post Reply
User avatar

Topic author
imiller
Master
Posts: 136
Joined: Fri Jun 28, 2019 8:45 am
Reputation: 0
Location: South Tyneside, UK
Status: Offline
Contact:

MACRO32 CONCODEXP messasge

Post by imiller » Thu Feb 23, 2023 9:21 am

While compiling on OpenVMS V9.2 x86-64 one of my programs written in MACRO32 I'm seeing these messages

example

probew #0, #4, (r1) ; check we can update the length
^
%XMAC-I-CONCODEXP, built-in used does not set condition codes; earlier instruction used instead

This is a very typical use of probew so I expect someone has seen this before. What should I use instead?
Ian Miller
[ personal opinion only. usual disclaimers apply. Do not taunt happy fun ball ].


fossman
Newbie
Posts: 3
Joined: Tue Sep 14, 2021 7:41 am
Reputation: 0
Status: Offline

Re: MACRO32 CONCODEXP messasge

Post by fossman » Mon Mar 13, 2023 2:44 pm

Ian,

I note this in the XCROSS release notes may well apply to the native x86 Macro command

You will see a message
%XMAC-I-CONCODEXP, built-in used does not set condition codes; earlier instruction used
instead
if you use the PROBER or PROBEW VAX instructions. On OpenVMS
x86, these are implemented via macros. The current macro
expansion triggers these false messages from the compiler.
The underlying macro expansion is correct. We'll remove
these messages in a future release.

There are some other interesting things things in those release notes as well

Cheers, Laurence

User avatar

Topic author
imiller
Master
Posts: 136
Joined: Fri Jun 28, 2019 8:45 am
Reputation: 0
Location: South Tyneside, UK
Status: Offline
Contact:

Re: MACRO32 CONCODEXP messasge

Post by imiller » Tue Mar 14, 2023 5:14 am

That's interesting. It's been a while since I installed the cross compilers. I guess I should install the latest and read the release notes.
Ian Miller
[ personal opinion only. usual disclaimers apply. Do not taunt happy fun ball ].

Post Reply