public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: David Miller <davem@davemloft.net>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
	"gcc-patches@gcc.gnu.org"	<gcc-patches@gcc.gnu.org>,
	"ro@CeBiTec.Uni-Bielefeld.DE"	<ro@CeBiTec.Uni-Bielefeld.DE>
Subject: Re: serious libgcc regression added recently
Date: Thu, 03 Nov 2011 14:17:00 -0000	[thread overview]
Message-ID: <4EB29DE0.6040007@oarcorp.com> (raw)
In-Reply-To: <20111102.183056.2300760196828501361.davem@davemloft.net>

On 11/02/2011 05:30 PM, David Miller wrote:
> From: Joel Sherrill<joel.sherrill@OARcorp.com>
> Date: Wed, 2 Nov 2011 16:29:16 -0500
>
>> Is this similar to what I just got for sparc-rtems when compiling
>> libgcc2 with -mcpu=v8?
>>
>> /tmp/cczMc4jN.s: Assembler messages:
>> /tmp/cczMc4jN.s:16: Error: Hardware capability "mul32" not enabled for
>> "smul".
>> /tmp/cczMc4jN.s:18: Error: Hardware capability "mul32" not enabled for
>> "smul".
>> /tmp/cczMc4jN.s:22: Error: Hardware capability "mul32" not enabled for
>> "umul".
>>
>> I can prepare a PR if you think it is different.
> I don't think so.  The bug I'm hitting seems to be simply that
> config/sparc/t-linux64 wasn't migrated up into the libgcc configure
> area properly the way that config/sparc/t-linux was.
>
> I'm working on a fix right now.
I filed a PR for this so it doesn't get lost.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50979

I am happy to retest whenever something changes.

Thanks.

-- 
Joel Sherrill, Ph.D.             Director of Research&  Development
joel.sherrill@OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
    Support Available             (256) 722-9985


      parent reply	other threads:[~2011-11-03 13:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02 20:49 David Miller
2011-11-02 22:10 ` Joel Sherrill
2011-11-02 22:52   ` David Miller
2011-11-02 23:06     ` David Miller
2011-11-03  0:22       ` David Miller
2011-11-03  0:23         ` Andrew Pinski
2011-11-03  1:25           ` David Miller
2011-11-03  0:35         ` Joseph S. Myers
2011-11-03  0:32       ` Joseph S. Myers
2011-11-03  1:51         ` David Miller
2011-11-03  3:22           ` Joseph S. Myers
2011-11-03  4:53             ` David Miller
2011-11-03  9:00               ` Paolo Bonzini
2011-11-03  9:16               ` Jakub Jelinek
2011-11-04  7:50                 ` David Miller
2011-11-05  3:23                 ` David Miller
2011-11-03 14:17     ` Joel Sherrill [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=4EB29DE0.6040007@oarcorp.com \
    --to=joel.sherrill@oarcorp.com \
    --cc=davem@davemloft.net \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=ro@CeBiTec.Uni-Bielefeld.DE \
    /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).