All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <darren.hart@intel.com>
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: Thu, 26 May 2011 14:16:57 -0700	[thread overview]
Message-ID: <4DDEC349.3000409@intel.com> (raw)
In-Reply-To: <03152273cac84eef23738c5f26c45b082194284f.1306442263.git.nitin.a.kamble@intel.com>

On 05/26/2011 01:41 PM, nitin.a.kamble@intel.com wrote:
> From: Nitin A Kamble <nitin.a.kamble@intel.com>
> 
> Fixes this bug [YOCTO #1105]
> 
> Working around this issue withg gcc 4.6.0 for beagleboard machine (armv7)
> 
> ccache arm-poky-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon
> -mfloat-abi=softfp -fno-tree-vectorize
> --sysroot=/build_disk/poky_build/build0/tmp/sysroots/beagleboard -c -I.
> -I../../../../src/gallium/include -I../../../../src/gallium/auxiliary
> -I../../../../src/gallium/drivers
> -I../../../../src/gallium/drivers/svga/include -O2 -pipe -g
> -feliminate-unused-debug-types -Wall -Wmissing-prototypes -std=c99 -ffast-math
> -fvisibility=hidden -fno-strict-aliasing -fPIC -D_GNU_SOURCE -DPTHREADS
> -DHAVE_POSIX_MEMALIGN -DUSE_XSHM -std=gnu99 -fvisibility=hidden -DHAVE_STDINT_H
> -DHAVE_SYS_TYPES_H svga_tgsi_insn.c -o svga_tgsi_insn.o
> svga_tgsi_insn.c: In function 'svga_shader_emit_instructions':
> svga_tgsi_insn.c:2969:1: internal compiler error: in push_minipool_fix, at
> config/arm/arm.c:12084
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <http://gcc.gnu.org/bugs.html> for instructions.
> make[4]: *** [svga_tgsi_insn.o] Error 1
> 
> Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
> ---
>  meta/recipes-graphics/mesa/mesa-xlib_7.10.2.bb |    3 +++
>  1 files changed, 3 insertions(+), 0 deletions(-)
> 
> diff --git a/meta/recipes-graphics/mesa/mesa-xlib_7.10.2.bb b/meta/recipes-graphics/mesa/mesa-xlib_7.10.2.bb
> index b77df2c..051bd72 100644
> --- a/meta/recipes-graphics/mesa/mesa-xlib_7.10.2.bb
> +++ b/meta/recipes-graphics/mesa/mesa-xlib_7.10.2.bb
> @@ -17,3 +17,6 @@ PE = "1"
>  PR = "r0"
>  
>  EXTRA_OECONF += "--with-driver=xlib"
> +
> +# nullify -O2

Can we specify why this is being done here in the recipe? We do this in
other areas, something like:

# GCC 4.6.0 hits an internal compiler error using -O2
# use -O to workaround.

This make it obvious when looking just at the source why this is an
issue, and will trigger a retest and removal when we move past 4.6.0.
Also, if there is a bug number, linking that here would make it easy to
determine if a fix is ready.

> +CFLAGS_append += " -O"

Thanks,

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel



  reply	other threads:[~2011-05-26 21:20 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 [this message]
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
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=4DDEC349.3000409@intel.com \
    --to=darren.hart@intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.