public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Marc Mengel <mengel@fnal.gov>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/8549: --pedantic-errors problems on RedHat 6.1
Date: Wed, 20 Nov 2002 06:59:00 -0000	[thread overview]
Message-ID: <20021113232601.28554.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/8549; it has been noted by GNATS.

From: Marc Mengel <mengel@fnal.gov>
To: Zack Weinberg <zack@codesourcery.com>
Cc: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: c++/8549: --pedantic-errors problems on RedHat 6.1
Date: Wed, 13 Nov 2002 17:24:01 -0600

 Zack Weinberg wrote:
 > bangerth@dealii.org writes:
 > 
 > 
 >>    So I think, the whole thing is attributable to the following:
 >>    Somewhen an extension in gcc was deprecated and the kernel
 >>    folks changed their header files accordingly.I think the
 >>    only way to make newer gccs work on these old systems
 >>    would be to fixinclude the respective header files, but I
 >>    doubt someone would like to put much energy in backporting
 >>    gcc to such old systems.
 > 
 > 
 > Note that the kernel has nothing to do with this.  The header
 > bits/mathinline.h is part of GNU libc.
 
 The point is, this is a case where --pedantic doesn't give
 a warning, but --pedantic-errors fails the compile.  That's the
 bug.  The fact that it's in an older glibc header file isn't
 neccesarily relevant to that point.  Either --pedantic should
 give a warning about it too, or --pedantic-errors shouldn't
 give an error.
 
 Of course the "old system" issue is relevant to the priority which one places 
 on fixing the bug, so I'm not saying the origin shouldn't be discussed,
 but I just want to remind folks what I thought the issue was.
 
 Marc Mengel
 


             reply	other threads:[~2002-11-13 23:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-20  6:59 Marc Mengel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-20  6:56 Zack Weinberg
2002-11-19 18:37 bangerth
2002-11-19 18:36 Marc Mengel
2002-11-19 18:02 bangerth
2002-11-19 16:10 mengel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021113232601.28554.qmail@sources.redhat.com \
    --to=mengel@fnal.gov \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).