From: Alexandre Oliva <aoliva@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Mathieu Imrazene <imrazene@nortelnetworks.com>, gcc@gcc.gnu.org
Subject: Re: GCC3.0.4 : Solaris 2.6 build failure
Date: Fri, 22 Feb 2002 14:27:00 -0000 [thread overview]
Message-ID: <orbseh40k4.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: Jakub Jelinek's message of "Fri, 22 Feb 2002 16:49:46 -0500"
On Feb 22, 2002, Jakub Jelinek <jakub@redhat.com> wrote:
> On Fri, Feb 22, 2002 at 06:46:23PM -0300, Alexandre Oliva wrote:
>> On Feb 22, 2002, Jakub Jelinek <jakub@redhat.com> wrote:
>>
>> > -mcpu=ultrasparc is different from -m64.
>>
>> What's your point? -mcpu=ultrasparc has problems in 3.0 just the same.
> Wasn't aware of problems with -mcpu=ultrasparc (have
> been using -mcpu=ultrasparc already in 2.96-RH quite extensively).
My understanding is that the problems with -mcpu=ultrasparc could only
be solved with SUBREG BYTE patch, that went into 2.96-RH.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer
next prev parent reply other threads:[~2002-02-22 22:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-22 7:09 Mathieu Imrazene
2002-02-22 13:28 ` Alexandre Oliva
2002-02-22 13:46 ` Jakub Jelinek
2002-02-22 13:51 ` Alexandre Oliva
2002-02-22 13:55 ` Jakub Jelinek
2002-02-22 14:27 ` Alexandre Oliva [this message]
2002-02-22 14:28 ` Jakub Jelinek
2002-02-22 15:30 ` Alexandre Oliva
2002-02-22 16:00 ` Craig Rodrigues
2002-02-22 19:56 lucier
2002-02-23 2:54 ` Jakub Jelinek
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=orbseh40k4.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=imrazene@nortelnetworks.com \
--cc=jakub@redhat.com \
/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).