* Re: __i386__ and cpp (Correction)
[not found] <m0y3WbW-0004ecC.cygnus.egcs@ocean.lucon.org>
@ 1998-02-13 23:13 ` Ulrich Drepper
1998-02-14 14:09 ` H.J. Lu
0 siblings, 1 reply; 6+ messages in thread
From: Ulrich Drepper @ 1998-02-13 23:13 UTC (permalink / raw)
To: egcs
hjl@lucon.org (H.J. Lu) writes:
> > __i386__ has been dropped from cpp in 1996. It
> > causes a problem for imake since it calls cpp
> > directly. It would be nice for egcs 1.0.2 to
> > define __i386__ on all x86 platforms.
> >
>
> Ooops. It should be i386 is checked by imake.
So why do you mention imake if it checks i386 and you want to get
__i386__ back? I don't understand. __i386__ cannot be a typo since
i386 is defined in the specs.
In fact, i386 is a problem since it violates the namespace. You
cannot get a ISO C compliant environment with gcc/egcs as it is.
-- Uli
---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,------------------' \ Sunnyvale, CA, 94089 USA
Cygnus Solutions `--' drepper at cygnus.com `-------------------------
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: __i386__ and cpp (Correction)
1998-02-13 23:13 ` __i386__ and cpp (Correction) Ulrich Drepper
@ 1998-02-14 14:09 ` H.J. Lu
1998-02-15 10:28 ` Jeffrey A Law
0 siblings, 1 reply; 6+ messages in thread
From: H.J. Lu @ 1998-02-14 14:09 UTC (permalink / raw)
To: drepper; +Cc: egcs
>
> hjl@lucon.org (H.J. Lu) writes:
>
> > > __i386__ has been dropped from cpp in 1996. It
> > > causes a problem for imake since it calls cpp
> > > directly. It would be nice for egcs 1.0.2 to
> > > define __i386__ on all x86 platforms.
> > >
> >
> > Ooops. It should be i386 is checked by imake.
>
> So why do you mention imake if it checks i386 and you want to get
> __i386__ back? I don't understand. __i386__ cannot be a typo since
> i386 is defined in the specs.
>
> In fact, i386 is a problem since it violates the namespace. You
> cannot get a ISO C compliant environment with gcc/egcs as it is.
>
We can try to make XFree86 to check __i386__. But we should give
something to imake to check within cpp.
--
H.J. Lu (hjl@gnu.org)
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: __i386__ and cpp (Correction)
1998-02-15 10:28 ` Jeffrey A Law
@ 1998-02-15 9:53 ` Ulrich Drepper
1998-02-15 14:58 ` Martin von Loewis
1 sibling, 0 replies; 6+ messages in thread
From: Ulrich Drepper @ 1998-02-15 9:53 UTC (permalink / raw)
To: law; +Cc: H.J. Lu, egcs
Jeffrey A Law <law@cygnus.com> writes:
> How about making "i386" available except when -ansi?
>
> That's what we do in this situation for other ports.
This is a first step. I think we should really prevent these symbols
from being defined by the compiler since they easily can conflict with
vars.
-- Uli
---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,------------------' \ Sunnyvale, CA, 94089 USA
Cygnus Solutions `--' drepper at cygnus.com `-------------------------
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: __i386__ and cpp (Correction)
1998-02-14 14:09 ` H.J. Lu
@ 1998-02-15 10:28 ` Jeffrey A Law
1998-02-15 9:53 ` Ulrich Drepper
1998-02-15 14:58 ` Martin von Loewis
0 siblings, 2 replies; 6+ messages in thread
From: Jeffrey A Law @ 1998-02-15 10:28 UTC (permalink / raw)
To: H.J. Lu; +Cc: drepper, egcs
In message < m0y3pmI-0004ecC@ocean.lucon.org >you write:
> >
> > hjl@lucon.org (H.J. Lu) writes:
> >
> > > > __i386__ has been dropped from cpp in 1996. It
> > > > causes a problem for imake since it calls cpp
> > > > directly. It would be nice for egcs 1.0.2 to
> > > > define __i386__ on all x86 platforms.
> > > >
> > >
> > > Ooops. It should be i386 is checked by imake.
> >
> > So why do you mention imake if it checks i386 and you want to get
> > __i386__ back? I don't understand. __i386__ cannot be a typo since
> > i386 is defined in the specs.
> >
> > In fact, i386 is a problem since it violates the namespace. You
> > cannot get a ISO C compliant environment with gcc/egcs as it is.
> >
>
> We can try to make XFree86 to check __i386__. But we should give
> something to imake to check within cpp.
How about making "i386" available except when -ansi?
That's what we do in this situation for other ports.
jeff
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: __i386__ and cpp (Correction)
1998-02-15 10:28 ` Jeffrey A Law
1998-02-15 9:53 ` Ulrich Drepper
@ 1998-02-15 14:58 ` Martin von Loewis
1 sibling, 0 replies; 6+ messages in thread
From: Martin von Loewis @ 1998-02-15 14:58 UTC (permalink / raw)
To: law; +Cc: hjl, drepper, egcs
> How about making "i386" available except when -ansi?
>
> That's what we do in this situation for other ports.
I'm sure this has been brought up before: Why is there no c89 front-end?
It should be easy to enable -ansi when argv[0] is "c89". Or, since this
is against the GNU coding standards, install another driver.
Regards,
Martin
^ permalink raw reply [flat|nested] 6+ messages in thread
* __i386__ and cpp (Correction)
@ 1998-02-13 17:41 H.J. Lu
0 siblings, 0 replies; 6+ messages in thread
From: H.J. Lu @ 1998-02-13 17:41 UTC (permalink / raw)
To: egcs
>
> __i386__ has been dropped from cpp in 1996. It
> causes a problem for imake since it calls cpp
> directly. It would be nice for egcs 1.0.2 to
> define __i386__ on all x86 platforms.
>
Ooops. It should be i386 is checked by imake.
--
H.J. Lu (hjl@gnu.org)
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~1998-02-15 14:58 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <m0y3WbW-0004ecC.cygnus.egcs@ocean.lucon.org>
1998-02-13 23:13 ` __i386__ and cpp (Correction) Ulrich Drepper
1998-02-14 14:09 ` H.J. Lu
1998-02-15 10:28 ` Jeffrey A Law
1998-02-15 9:53 ` Ulrich Drepper
1998-02-15 14:58 ` Martin von Loewis
1998-02-13 17:41 H.J. Lu
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).