This is the mail archive of the 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]
Other format: [Raw text]

Re: inline asm string/line break rules change

Andi Kleen wrote:
> On Sun, Apr 14, 2002 at 05:08:35AM -0400, Tim Hollebeek wrote:
> > On Sun, Apr 14, 2002 at 10:46:29AM +0200, Andi Kleen wrote:
> > > On Sun, Apr 14, 2002 at 01:28:43AM -0400, Tim Hollebeek wrote:
> > > >
> > > > > Andi, don't use modern compilers with old broken source bases.
> > > >
> > > > Or: if you do, ignore any warnings you get.
> > >
> > > That's not an option if you need the other warnings.
> > > And unfortunately this warning cannot be turned off.
> >
> > grep is your friend.
> Well, assuming this functionality is really removed as the warning
> threatens to do then this won't help in gcc 3.2, no ?  If it is not
> removed then the warning is completely pointless.

The funtionality is really removed.  And gcc 3.0 did not work well
enough to get extensive use in the RTEMS community, so the warnings
were ignored.  We were more worried about getting all the target
CPUs we cared about working again.

Sounds like the bottom line is that newlib and RTEMS need to change

If a script to fix this is so trivial, does someone already have one. :)

> -Andi

Joel Sherrill, Ph.D.             Director of Research & Development                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (256) 722-9985

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