public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* gcc.dg/c90-intconst-1.c
@ 2003-05-17 18:18 Eric Christopher
  2003-05-17 20:31 ` gcc.dg/c90-intconst-1.c Joseph S. Myers
  0 siblings, 1 reply; 7+ messages in thread
From: Eric Christopher @ 2003-05-17 18:18 UTC (permalink / raw)
  To: jsm28; +Cc: gcc

I don't think that this test can pass without warnings on any newlib
target. Perhaps we should XFAIL for this, or is there a way to turn off
the #include_next warning without turning off the rest that I was't able
to find? :)

-eric

-- 
Eric Christopher <echristo@redhat.com>

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: gcc.dg/c90-intconst-1.c
  2003-05-17 18:18 gcc.dg/c90-intconst-1.c Eric Christopher
@ 2003-05-17 20:31 ` Joseph S. Myers
  2003-05-17 22:06   ` gcc.dg/c90-intconst-1.c Eric Christopher
  0 siblings, 1 reply; 7+ messages in thread
From: Joseph S. Myers @ 2003-05-17 20:31 UTC (permalink / raw)
  To: Eric Christopher; +Cc: gcc

On Sat, 17 May 2003, Eric Christopher wrote:

> I don't think that this test can pass without warnings on any newlib
> target. Perhaps we should XFAIL for this, or is there a way to turn off

You haven't explained what the problem is supposed to be.  This test is
meant to be portable to all targets on which long is no more than 64 bits.
(Though some hosts with insufficient memory or stack space might have
problems compiling this testcase or c99-intconst-1.c.)

-- 
Joseph S. Myers
jsm28@cam.ac.uk

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: gcc.dg/c90-intconst-1.c
  2003-05-17 20:31 ` gcc.dg/c90-intconst-1.c Joseph S. Myers
@ 2003-05-17 22:06   ` Eric Christopher
  2003-05-17 22:23     ` gcc.dg/c90-intconst-1.c Joseph S. Myers
  0 siblings, 1 reply; 7+ messages in thread
From: Eric Christopher @ 2003-05-17 22:06 UTC (permalink / raw)
  To: Joseph S. Myers; +Cc: gcc

On Sat, 2003-05-17 at 12:40, Joseph S. Myers wrote:
> On Sat, 17 May 2003, Eric Christopher wrote:
> 
> > I don't think that this test can pass without warnings on any newlib
> > target. Perhaps we should XFAIL for this, or is there a way to turn off
> 
> You haven't explained what the problem is supposed to be.  This test is
> meant to be portable to all targets on which long is no more than 64 bits.
> (Though some hosts with insufficient memory or stack space might have
> problems compiling this testcase or c99-intconst-1.c.)

Sorry about that. The newlib version of limits.h uses #include_next.

-eric

-- 
Eric Christopher <echristo@redhat.com>

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: gcc.dg/c90-intconst-1.c
  2003-05-17 22:06   ` gcc.dg/c90-intconst-1.c Eric Christopher
@ 2003-05-17 22:23     ` Joseph S. Myers
  2003-05-18  0:02       ` gcc.dg/c90-intconst-1.c Eric Christopher
  0 siblings, 1 reply; 7+ messages in thread
From: Joseph S. Myers @ 2003-05-17 22:23 UTC (permalink / raw)
  To: Eric Christopher; +Cc: gcc

On Sat, 17 May 2003, Eric Christopher wrote:

> Sorry about that. The newlib version of limits.h uses #include_next.

But this shouldn't generate a warning because <limits.h> should be a 
system header.  If the compiler is getting run with the relevant directory 
not counted as a system header, then it is the test harness that should be 
fixed to use -isystem where appropriate.

-- 
Joseph S. Myers
jsm28@cam.ac.uk

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: gcc.dg/c90-intconst-1.c
  2003-05-17 22:23     ` gcc.dg/c90-intconst-1.c Joseph S. Myers
@ 2003-05-18  0:02       ` Eric Christopher
  2003-05-19  8:31         ` DejaGnu (was: gcc.dg/c90-intconst-1.c) Gerald Pfeifer
  2003-05-19 20:55         ` gcc.dg/c90-intconst-1.c Mike Stump
  0 siblings, 2 replies; 7+ messages in thread
From: Eric Christopher @ 2003-05-18  0:02 UTC (permalink / raw)
  To: Joseph S. Myers; +Cc: gcc

On Sat, 2003-05-17 at 15:06, Joseph S. Myers wrote:
> On Sat, 17 May 2003, Eric Christopher wrote:
> 
> > Sorry about that. The newlib version of limits.h uses #include_next.
> 
> But this shouldn't generate a warning because <limits.h> should be a 
> system header.  If the compiler is getting run with the relevant directory 
> not counted as a system header, then it is the test harness that should be 
> fixed to use -isystem where appropriate.

I'm not sure I understand so I'll try repeating what you said a
different way :)

-pedantic shouldn't warn for system header files
the newlib header files should probably be preferenced with -isystem to
avoid these kinds of warnings like this. Need to change dejagnu's
libgloss.exp for this. Anyone know where the current dejagnu repository
is and who is in charge?

-eric

-- 
Eric Christopher <echristo@redhat.com>

^ permalink raw reply	[flat|nested] 7+ messages in thread

* DejaGnu (was: gcc.dg/c90-intconst-1.c)
  2003-05-18  0:02       ` gcc.dg/c90-intconst-1.c Eric Christopher
@ 2003-05-19  8:31         ` Gerald Pfeifer
  2003-05-19 20:55         ` gcc.dg/c90-intconst-1.c Mike Stump
  1 sibling, 0 replies; 7+ messages in thread
From: Gerald Pfeifer @ 2003-05-19  8:31 UTC (permalink / raw)
  To: Eric Christopher; +Cc: Joseph S. Myers, gcc

On Sun, 17 May 2003, Eric Christopher wrote:
> Anyone know where the current dejagnu repository is and who is in
> charge?

http://www.gnu.org/software/dejagnu/

  The latest dejagnu development sources are available via anonymous CVS.
  Use the following commands to check them out (just hit return when you
  are prompted for the password):

    $ cvs -z3 -d :pserver:anoncvs@subversions.gnu.org:/cvsroot/dejagnu login
    Password: [Hit EnterKey]
    $ cvs -z3 -d :pserver:anoncvs@subversions.gnu.org:/cvsroot/dejagnu co dejagnu
  :
  DejaGnu is currently being maintained by Rob Savoye <rob@welcomehome.org>.

(Rob responded to email last year and seemed active back then; I don't
know what happened since then.)

Gerald
-- 
Gerald "Jerry"   pfeifer@dbai.tuwien.ac.at   http://www.pfeifer.com/gerald/

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: gcc.dg/c90-intconst-1.c
  2003-05-18  0:02       ` gcc.dg/c90-intconst-1.c Eric Christopher
  2003-05-19  8:31         ` DejaGnu (was: gcc.dg/c90-intconst-1.c) Gerald Pfeifer
@ 2003-05-19 20:55         ` Mike Stump
  1 sibling, 0 replies; 7+ messages in thread
From: Mike Stump @ 2003-05-19 20:55 UTC (permalink / raw)
  To: Eric Christopher; +Cc: Joseph S. Myers, gcc

On Saturday, May 17, 2003, at 04:06 PM, Eric Christopher wrote:
> Need to change dejagnu's libgloss.exp for this. Anyone know where the 
> current dejagnu repository is and who is in charge?

bug-dejagnu@gnu.org, as documented in the manual.

lair bash[3] cd dejagnu
lair bash[5] cat CVS/Root
:pserver:anoncvs@subversions.gnu.org:/cvsroot/dejagnu
lair bash[6] cat CVS/Repository
/cvsroot/dejagnu/dejagnu

Him name is Rob.

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2003-05-19 20:52 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-05-17 18:18 gcc.dg/c90-intconst-1.c Eric Christopher
2003-05-17 20:31 ` gcc.dg/c90-intconst-1.c Joseph S. Myers
2003-05-17 22:06   ` gcc.dg/c90-intconst-1.c Eric Christopher
2003-05-17 22:23     ` gcc.dg/c90-intconst-1.c Joseph S. Myers
2003-05-18  0:02       ` gcc.dg/c90-intconst-1.c Eric Christopher
2003-05-19  8:31         ` DejaGnu (was: gcc.dg/c90-intconst-1.c) Gerald Pfeifer
2003-05-19 20:55         ` gcc.dg/c90-intconst-1.c Mike Stump

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).