All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11991] [numpy] segfault when compiling for RPi3 64bits
Date: Fri, 05 Jul 2019 21:11:43 +0000	[thread overview]
Message-ID: <bug-11991-163-p2QCcxwRVg@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11991-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=11991

--- Comment #1 from Peter Seiderer <ps.report@gmx.net> ---
Which GCC version? Mind to share your config/defconfig?

There is one more reference of the same compile failure on the web, see [1].

numpy/core/src/npymath/npy_math_internal.h.src:482:12: internal compiler error:
Segmentation fault
     return @kind@@c@(x, y);
            ^~~~~~~~~~~~~~~

Stating 'Bug does not occur when using -O0 on GCC 8.2.0 and does not occur at
all with GCC 9.1.0', mind to try a different compiler and/or optimization
setting?

Regards,
Peter

[1] https://github.com/numpy/numpy/issues/13622

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2019-07-05 21:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-26 12:50 [Buildroot] [Bug 11991] New: [numpy] segfault when compiling for RPi3 64bits bugzilla at busybox.net
2019-07-05 21:11 ` bugzilla at busybox.net [this message]
2019-07-08 11:36 ` [Buildroot] [Bug 11991] " bugzilla at busybox.net
2019-07-08 20:25 ` bugzilla at busybox.net
2019-07-10  6:30 ` bugzilla at busybox.net
2019-07-12 19:33 ` bugzilla at busybox.net
2019-07-15  5:38 ` bugzilla at busybox.net

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=bug-11991-163-p2QCcxwRVg@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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.