All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH][morty] gcc6: Upgrade to 6.4.0 (latest stable series release)
Date: Mon, 5 Mar 2018 11:45:06 +0100	[thread overview]
Message-ID: <20180305104506.GA19075@jama> (raw)
In-Reply-To: <CAJ86T=VFg7cfFhUJYssODc5KwdfnBLG9VLbENU+j8ExKmkB57w@mail.gmail.com>

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

On Mon, Mar 05, 2018 at 01:51:59AM -0800, Andre McCurdy wrote:
> On Mon, Mar 5, 2018 at 1:19 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
> > Thanks Andre!
> >
> > I've seen another failure probably caused by this gcc upgrade in morty-next:
> >
> > python-matplotlib triggers ICE:
> >
> > src/_png.cpp: In function 'void init_png()':
> > src/_png.cpp:497:25: warning: variable '_png' set but not used
> > [-Wunused-but-set-variable]
> >      static _png_module* _png = NULL;
> >                          ^~~~
> > src/_png.cpp: In member function 'Py::Object _png_module::read_png(const
> > Py::Tuple&)':
> > src/_png.cpp:272:1: internal compiler error: Segmentation fault
> >  _png_module::read_png(const Py::Tuple& args)
> >  ^~~~~~~~~~~
> > Please submit a full bug report,
> > with preprocessed source if appropriate.
> > See <http://gcc.gnu.org/bugs.html> for instructions.
> > error: command 'i586-oe-linux-gcc' failed with exit status 1
> > ERROR: Function failed: do_compile (log file is located at
> > python-matplotlib/1.1.0-r1/temp/log.do_compile.15213)
> >
> > I'll try to build it with Khem's and Andre's patches only to eliminate
> > hjl/indirect/gcc-6-branch/master changes.
> >
> 
> FWIW, I see the same error with my OE 2.2 + gcc 6.4.0 based distro.
> The ICE only happens if I build with -O2 though (the build is clean
> with -Os, which I use by default).
> 
> In case it's useful to anyone, my branch of morty with a gcc 6.4.0 backport is:
> 
>   git clone https://github.com/lgirdk/openembedded-core.git --branch oe22b

You're right with 14 cherry-picks from your branch instead of 6.4
upgrade from Juro

8e6e2e3 gcc6: enable FL_LPAE flag for armv7ve cores
756e8f2 gcc6: Fix unaligned STRD issue on ARM
33e717b tcmode-default.inc: update GCCVERSION 6.3 -> 6.4
bb03bfd gcc6: Upgrade to 6.4
cf3be39 gcc-runtime: Disable libitm on riscv
8e0fa79 gcc-6.3: Backport patch to fix ICE on ARM
a77c5c4 gcc-6.3.inc: Use ucontext_t not struct ucontext.
c5376cb gcc-6.3: backport fix of check for empty string in ubsan.c
322dd7f gcc: Remove unused patch
07e888e gcc: Fix CVE-2016-6131 in libiberty
8c5205d gcc-6: Add fix for missing no-PIE flags
cf3da73 gcc-6: Sync gcc stddef.h with musl stddef.h
953f3e2 gcc6: Upgrade to 6.3.0
60ded51 Revert "gcc-6.2: backport fix of check for empty string in ubsan.c"

I can still reproduce it with -O2 and doesn't fail with -Os.

It also doesn't fail with matplotlib 2.0.2 version if I cherry-pick:
commit 10c8c39c25d902ab5268fa48ac2bc0e42e65b179
Author: Khem Raj <raj.khem@gmail.com>
Date:   Fri Sep 1 15:27:20 2017 -0700

    python-matplotlib: Upgrade to 2.0.2

from meta-oe/rocko as well.

Thanks

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

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

  reply	other threads:[~2018-03-05 10:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-04 11:21 [PATCH][morty] gcc6: Upgrade to 6.4.0 (latest stable series release) Richard Purdie
2018-03-04 11:35 ` ✗ patchtest: failure for " Patchwork
2018-03-04 14:15 ` [PATCH][morty] " Martin Jansa
2018-03-04 16:22   ` Martin Jansa
2018-03-05  6:37     ` Andre McCurdy
2018-03-05  9:19       ` Martin Jansa
2018-03-05  9:51         ` Andre McCurdy
2018-03-05 10:45           ` Martin Jansa [this message]
2018-03-06  2:31             ` Andre McCurdy

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=20180305104506.GA19075@jama \
    --to=martin.jansa@gmail.com \
    --cc=armccurdy@gmail.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.