From: Eric Botcazou <ebotcazou@libertysurf.fr>
To: Gabriel Dos Reis <gdr@integrable-solutions.net>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [3.3] Fix code assembling for UltraSPARC III on Solaris
Date: Mon, 12 Jul 2004 19:58:00 -0000 [thread overview]
Message-ID: <200407121520.32161.ebotcazou@libertysurf.fr> (raw)
In-Reply-To: <200407051312.29492.ebotcazou@libertysurf.fr>
> May I backport the following patch to the 3.3 branch after the usual
> testing? http://gcc.gnu.org/ml/gcc-patches/2004-02/msg00022.html
>
> The problem is still present as of today (I planned to fix it for 3.3.4
> but completely forgot to do so).
The problem is pretty annoying so I've commited the patch on the 3.3 branch
(minus the "Remove -mcpu=v8plus" bits) after bootstrapping/regtesting on:
sparc64-sun-solaris2.9
sparc-sun-solaris2.8
sparc-sun-solaris2.7
sparc-sun-solaris2.6
sparc-sun-solaris2.5.1
--
Eric Botcazou
prev parent reply other threads:[~2004-07-12 13:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-05 12:07 Eric Botcazou
2004-07-09 10:11 ` Eric Botcazou
2004-07-12 19:58 ` Eric Botcazou [this message]
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=200407121520.32161.ebotcazou@libertysurf.fr \
--to=ebotcazou@libertysurf.fr \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
/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).