Re: pre-processor symbols and gcc -v

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



kevin diggs <diggskevin38@xxxxxxxxx> writes:

> If a pre-processor macro, say __m68k__ is defined shouldn't it show up
> in gcc -v? gcc version is 3.4.6.

gcc -v does not list predefined preprocessor macros.  You can see them
by running "gcc -x c /dev/null -E -dM".

> P.S.:  Anyone point me to an example of how to use the 68k 'Q' constraint?

In what sense?  There are various examples in gcc/config/m68k/m68k.md,
e.g., tst<mode>_cf.

> And while I'm here, anyway to see when an instruction causes an
> unimplemented instruction trap (like fcos on a 68040)?

I guess I don't understand the question.

Ian


[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux