From: lucier@math.purdue.edu
To: gcc@gcc.gnu.org
Cc: lucier@math.purdue.edu
Subject: Re: GCC3.0.4 : Solaris 2.6 build failure
Date: Fri, 22 Feb 2002 19:56:00 -0000 [thread overview]
Message-ID: <200202230353.g1N3rk627178@banach.math.purdue.edu> (raw)
Re: The discussion about whether -mcpu=ultrasparc works on gcc-3.0.4
My experience with -mcpu=ultrasparc on the 3.0.* series is that it
doesn't work worth a damn.
Even on the mainline, routines are effectively restricted to < 128Kbytes
in size on sparcv9 (see PR 5626; the commentary there says that that
the limit is 256Kbytes, but that is incorrect).
So, for my purposes, the mainline sparcv9 port of gcc 3.1 doesn't work,
either.
Brad
next reply other threads:[~2002-02-23 3:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-22 19:56 lucier [this message]
2002-02-23 2:54 ` Jakub Jelinek
-- strict thread matches above, loose matches on Subject: below --
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
2002-02-22 14:28 ` Jakub Jelinek
2002-02-22 15:30 ` Alexandre Oliva
2002-02-22 16:00 ` Craig Rodrigues
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=200202230353.g1N3rk627178@banach.math.purdue.edu \
--to=lucier@math.purdue.edu \
--cc=gcc@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).