Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] Fix for gcc bug 61144
Date: Fri, 10 Oct 2014 12:43:23 +0200	[thread overview]
Message-ID: <20141010104323.GL12322@jama> (raw)
In-Reply-To: <543689B7.5050109@urbanec.net>

[-- Attachment #1: Type: text/plain, Size: 3244 bytes --]

On Fri, Oct 10, 2014 at 12:12:23AM +1100, Peter Urbanec wrote:
> See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61144 for details.
> 
> This patch is taken from the gcc repository and should be obsoleted by a 
> gcc release after 4.9.1
> 
> The problem is severe enough (at least from my point of view) to need 
> this patch until the next gcc release is available.

Wrong MP, this belongs to oe-core ML.

> commit 03ae7912aadbf3b55b966a1367f07c7dbbddda80
> Author: Peter Urbanec
> Date:   Fri Oct 10 00:03:28 2014 +1100
> 
>     gcc: Patch for gcc bug 61144.
>     
>     This fixes gcc bug 6144, which in my case exhibited itself as a kernel
>     module that failed to load. This was because static platform_data
>     structures were being corrupted with the optimiser being set to any
>     value other than -O0.
> 
> diff --git a/meta/recipes-devtools/gcc/gcc-4.9.inc b/meta/recipes-devtools/gcc/gcc-4.9.inc
> index 25778bd..9a66cd2 100644
> --- a/meta/recipes-devtools/gcc/gcc-4.9.inc
> +++ b/meta/recipes-devtools/gcc/gcc-4.9.inc
> @@ -70,6 +70,7 @@ SRC_URI = "\
>      file://0053-gcc-fix-segfault-from-calling-free-on-non-malloc-d-a.patch \
>      file://0054-gcc-Makefile.in-fix-parallel-building-failure.patch \
>      file://0055-PR-rtl-optimization-61801.patch \
> +    file://0056-top-level-reorder_gcc-bug-61144.patch \
>  "
>  SRC_URI[md5sum] = "fddf71348546af523353bd43d34919c1"
>  SRC_URI[sha256sum] = "d334781a124ada6f38e63b545e2a3b8c2183049515a1abab6d513f109f1d717e"
> diff --git a/meta/recipes-devtools/gcc/gcc-4.9/0056-top-level-reorder_gcc-bug-61144.patch b/meta/recipes-devtools/gcc/gcc-4.9/0056-top-level-reorder_gcc-bug-61144.patch
> new file mode 100644
> index 0000000..11fa969
> --- /dev/null
> +++ b/meta/recipes-devtools/gcc/gcc-4.9/0056-top-level-reorder_gcc-bug-61144.patch
> @@ -0,0 +1,25 @@
> +--- /dev/null
> ++++ b/meta/recipes-devtools/gcc/gcc-4.9/0056-top-level-reorder_gcc-bug-61144.patch
> +@@ -0,0 +1,21 @@
> ++--- a/gcc/varpool.c    2014/10/05 02:50:01     215895
> +++++ b/gcc/varpool.c    2014/10/05 04:52:19     215896
> ++@@ -329,8 +329,16 @@
> ++
> ++   /* Variables declared 'const' without an initializer
> ++      have zero as the initializer if they may not be
> ++-     overridden at link or run time.  */
> ++-  if (!DECL_INITIAL (real_decl)
> +++     overridden at link or run time.
> +++
> +++     It is actually requirement for C++ compiler to optimize const variables
> +++     consistently. As a GNU extension, do not enfore this rule for user defined
> +++     weak variables, so we support interposition on:
> +++     static const int dummy = 0;
> +++     extern const int foo __attribute__((__weak__, __alias__("dummy")));
> +++   */
> +++  if ((!DECL_INITIAL (real_decl)
> +++       || (DECL_WEAK (decl) && !DECL_COMDAT (decl)))
> ++       && (DECL_EXTERNAL (decl) || decl_replaceable_p (decl)))
> ++     return error_mark_node;
> ++ 
> +

> -- 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel


-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

      reply	other threads:[~2014-10-10 10:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-09 13:12 [PATCH] Fix for gcc bug 61144 Peter Urbanec
2014-10-10 10:43 ` Martin Jansa [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=20141010104323.GL12322@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-devel@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