From: Phil Blundell <pb@pbcl.net>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [bugfix 1/1] mesa-xlib: workaround gcc 4.6.0 ICE
Date: Fri, 27 May 2011 16:06:44 +0100 [thread overview]
Message-ID: <1306508804.2525.460.camel@phil-desktop> (raw)
In-Reply-To: <1306452822.27470.220.camel@rex>
On Fri, 2011-05-27 at 00:33 +0100, Richard Purdie wrote:
> I talked about this on IRC but simply put, no way.
>
> The problem is:
>
> a) Arm specific
> b) determined now to be armv7 specific
> c) gcc version specific
>
> and the fix should reflect this.
From a fairly superficial look at the crash I suspect you probably want
something like:
--- arm.md~ 2011-05-27 15:18:31.916926254 +0100
+++ arm.md 2011-05-27 15:31:57.331525688 +0100
@@ -4213,7 +4213,9 @@
uxth%?\\t%0, %1
ldr%(h%)\\t%0, %1"
[(set_attr "type" "alu_shift,load_byte")
- (set_attr "predicable" "yes")]
+ (set_attr "predicable" "yes")
+ (set_attr "pool_range" "*,256")
+ (set_attr "neg_pool_range" "*,244")]
)
(define_insn "*arm_zero_extendhisi2addsi"
It also looks like this could happen on ARMv6 as well, for what that's
worth, though I haven't tested to see whether it actually does or not.
p.
next prev parent reply other threads:[~2011-05-27 15:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 20:41 [bugfix 0/1] workaround for gcc 4.6.0 issue on beagleboard nitin.a.kamble
2011-05-26 20:41 ` [bugfix 1/1] mesa-xlib: workaround gcc 4.6.0 ICE nitin.a.kamble
2011-05-26 21:16 ` Darren Hart
2011-05-26 21:22 ` Kamble, Nitin A
2011-05-26 23:33 ` Richard Purdie
2011-05-27 0:37 ` Khem Raj
2011-05-27 1:03 ` Kamble, Nitin A
2011-05-27 7:14 ` Koen Kooi
2011-05-27 8:54 ` Richard Purdie
2011-05-27 9:30 ` Phil Blundell
2011-05-27 17:11 ` Richard Purdie
2011-05-27 15:06 ` Phil Blundell [this message]
2011-05-27 17:13 ` Kamble, Nitin A
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=1306508804.2525.460.camel@phil-desktop \
--to=pb@pbcl.net \
--cc=openembedded-core@lists.openembedded.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