Message 336205 - Python tracker

Message336205

Author Michael.Felt
Recipients Michael.Felt, izbyshev
Date 2019-02-21.11:19:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <57cbd6da-b94f-49e0-2d38-1d3c67acf2ab@felt.demon.nl>
In-reply-to <1550608185.88.0.0973450009509.issue36034@roundup.psfhosted.org>
Content
xlc has an option -qsource that creates output like this - first showing
the code with macro, then showing the expansion

>>>>> SOURCE SECTION <<<<<
...
       16 |         dev = st.st_dev;
       17 |         minor = minor(dev);
       17 +         minor = (int)((dev)&0xFFFF);
       18 |         major = major(dev);
       18 +         major = (int)((unsigned)(dev)>>16);

I'll check and see if -E processes the output in the same way. Thx.

On 2/19/2019 9:29 PM, Alexey Izbyshev wrote:
> Alexey Izbyshev <izbyshev@ispras.ru> added the comment:
>
> I don't know what you mean by "in-line" pre-processing output, but you can use -E option to get the normal preprocessor output. Line directives will tell you where those functions come from on a system where there is no compilation error.
>
> Of course, if those functions are defined in some other headers on AIX 6.1, it won't help you, so you might as well just grep /usr/include :)
>
> ----------
> nosy: +izbyshev
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue36034>
> _______________________________________
>
History
Date User Action Args
2019-02-21 11:19:04Michael.Feltsetrecipients: + Michael.Felt, izbyshev
2019-02-21 11:19:04Michael.Feltlinkissue36034 messages
2019-02-21 11:19:04Michael.Feltcreate