public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sebastian-gcc at sipsolutions dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/100788] Internal compiler error related to #line macros(?)
Date: Thu, 27 May 2021 16:20:28 +0000	[thread overview]
Message-ID: <bug-100788-4-jvo3xIXzz9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100788-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100788

--- Comment #9 from seberg <sebastian-gcc at sipsolutions dot net> ---
NumPy is pretty light weight (at least on linux systems, and if you do not care
about setting up BLAS manually).  You probably only need the Python dev
headers, that I expect you already have.

Hopefully, the following will just work for you:

git clone https://github.com/numpy/numpy
cd numpy
python runtests.py --show-build-log --gcov
# If you got problems due to blas/lapack, try with NPY_BLAS_ORDER=""

which will leave all the temporary files on error and print out the compiler
options.  (There is some spammy output at the very end to scroll past, and the
exact commands are the concatenation of the print out -- but the erroring one
is printed in full after the GCC error.)

  parent reply	other threads:[~2021-05-27 16:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-27  4:22 [Bug gcov-profile/100788] New: " sebastian-gcc at sipsolutions dot net
2021-05-27  4:48 ` [Bug gcov-profile/100788] " sebastian-gcc at sipsolutions dot net
2021-05-27  6:56 ` marxin at gcc dot gnu.org
2021-05-27  7:03 ` sebastian-gcc at sipsolutions dot net
2021-05-27  7:07 ` marxin at gcc dot gnu.org
2021-05-27  7:21 ` sebastian-gcc at sipsolutions dot net
2021-05-27  7:24 ` marxin at gcc dot gnu.org
2021-05-27  7:30 ` sebastian-gcc at sipsolutions dot net
2021-05-27  7:34 ` marxin at gcc dot gnu.org
2021-05-27 16:20 ` sebastian-gcc at sipsolutions dot net [this message]
2021-05-28 11:04 ` marxin at gcc dot gnu.org
2021-06-03  0:32 ` sebastian-gcc at sipsolutions dot net
2021-06-10 14:40 ` marxin at gcc dot gnu.org
2021-06-11 10:00 ` cvs-commit at gcc dot gnu.org
2021-06-11 10:01 ` marxin at gcc dot gnu.org
2021-08-13 13:50 ` cvs-commit at gcc dot gnu.org
2021-08-13 13:59 ` cvs-commit at gcc dot gnu.org
2021-08-13 14:00 ` marxin at gcc dot gnu.org
2021-12-10 20:20 ` pinskia at gcc dot gnu.org
2021-12-10 20:21 ` pinskia at gcc dot gnu.org

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-100788-4-jvo3xIXzz9@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).