public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Volker Reichelt <reichelt@igpm.rwth-aachen.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: other/8948: [3.3 regression] Definition of __i686 causes big Problems
Date: Wed, 08 Jan 2003 09:46:00 -0000	[thread overview]
Message-ID: <20030108094602.3825.qmail@sources.redhat.com> (raw)

The following reply was made to PR other/8948; it has been noted by GNATS.

From: Volker Reichelt <reichelt@igpm.rwth-aachen.de>
To: jbuck@synopsys.com
Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, norbert_wolff@t-online.de
Subject: Re: other/8948: [3.3 regression] Definition of __i686 causes big Problems
Date: Wed, 8 Jan 2003 11:37:08 +0100

 On  7 Jan, Joe Buck wrote:
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8948
 > 
 > The definition of __i686 has been present in gcc all along; removing it will
 > cause other regressions (any code that depends on it will break), so 
 > that's not an
 > option.
 > 
 > Will glibc-2.3.1 build with older gcc's?  If so, why isn't there trouble 
 > from
 > sysdep.h in such cases?
 > 
 > Volker, you are calling this a regression, but do older gcc's actually work?
 > If so, how?  They define __i686 too, in exactly the same way.
 
 I marked it as a regression according to the submitter's remark "so this
 library cannot be compiled any more for i686". I didn't actually check,
 but the problem sounded severe, so that I marked it as a regresion
 anyway, just to be sure that it gets attention.
 
 I should have been more explicit about that, sorry.
 
 Regards,
 Volker
 
 


             reply	other threads:[~2003-01-08  9:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08  9:46 Volker Reichelt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-11  0:21 jbuck
2003-01-08  1:56 Joe Buck
2002-12-16  9:23 reichelt

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=20030108094602.3825.qmail@sources.redhat.com \
    --to=reichelt@igpm.rwth-aachen.de \
    --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).