This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: tradtradcpp0, cpp spec bugs, and use of '|'


Richard Henderson <rth@redhat.com> writes:
> On Tue, Nov 21, 2000 at 10:53:00PM +0900, Neil Booth wrote:
> > Clearly no-one uses this stuff, otherwise it would have come up.
> 
> On the contrary -- quite a few places do.  It's just that you
> don't normally write "-march=pentium -march=i586" do you?

well, that and:

(1) if you're turning a flag into other flags, quite often those other
flags will work if specified multiple times.  e.g.:

	%{march=pentium|march=i586: -foobar}

will output -foobar twice, and that's probably OK.

(2) i'm sure that at least some things which are in '|' specs also
show up in specs on their own on occasion (or in specs where they're
wildcarded)...  Which means that they'll get matched in other places.


I don't know what all uses there are of '|', but I could easily
believe that the case of _needing_ to chop up '|' specs to mark flags
valid hasn't been an issue before, even with who knows how many other
uses of '|'.


(of course, it's not clear to me that a case like the one above would
_benefit_ from the 'for each matching, do the output' behaviour of
existing '|' either.)



chris

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]