public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: <martin@bruli.net>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: RE: optimization/8873: Optimization on alpha (ev5)
Date: Tue, 18 Feb 2003 17:16:00 -0000	[thread overview]
Message-ID: <20030218171601.4558.qmail@sources.redhat.com> (raw)

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

From: <martin@bruli.net>
To: <ebotcazou@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>,
       <martin@bruli.net>, <nobody@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org>
Cc:  
Subject: RE: optimization/8873: Optimization on alpha (ev5)
Date: Tue, 18 Feb 2003 18:14:32 +0100

 Hi,
 
 No I can't.
 The last gcc version you can compile and run all off
 - linux-2.4
 - glibc-2.2.5
 - modutils-2.4
 is 2.95.3. All later version will generate invalid (not runnable
 code) on my alphas. And I have tested _all_ versions after 2.95.3.
 No I went back to 2.95.3 with the disadvantage that the most
 recent glibc version that can be compiled is 2.2.5.
 
 Regards,
 Martin
 
 > -----Original Message-----
 > From: ebotcazou@gcc.gnu.org [mailto:ebotcazou@gcc.gnu.org]=20
 > Sent: Tuesday, February 18, 2003 2:40 PM
 > To: gcc-bugs@gcc.gnu.org; gcc-prs@gcc.gnu.org;=20
 > martin@bruli.net; nobody@gcc.gnu.org
 > Subject: Re: optimization/8873: Optimization on alpha (ev5)
 >=20
 >=20
 > Synopsis: Optimization on alpha (ev5)
 >=20
 > State-Changed-From-To: open->feedback
 > State-Changed-By: ebotcazou
 > State-Changed-When: Tue Feb 18 13:40:08 2003
 > State-Changed-Why:
 >     We need more information to identify the problem. Could=20
 > you narrow it down to a specific chunk of code?
 >=20
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-trail&database=3D=
 gcc&p
 r=3D8873
 


             reply	other threads:[~2003-02-18 17:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-18 17:16 martin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-07  9:36 martin
2003-02-19  9:06 Eric Botcazou
2003-02-18 13:40 ebotcazou
2002-12-08 15:46 Falk Hueffner
2002-12-08  7:16 martin

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=20030218171601.4558.qmail@sources.redhat.com \
    --to=martin@bruli.net \
    --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).