public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <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, 10 Jun 2021 14:40:38 +0000	[thread overview]
Message-ID: <bug-100788-4-dLc7dtchIu@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 #12 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to seberg from comment #11)
> Does that mean that fixing the `#line` directives (or inserting additional
> ones) should be able to fix the issue?  (Or work around it, if you consider
> it a bug.)

Yes. I've got an approved patch for the current master:
https://gcc.gnu.org/pipermail/gcc-patches/2021-June/571593.html

For older releases, I consider relaxation of the assert.

> 
> I tried to figure out where the `#line` directives currently causes this
> situation, and add new ones in some places in the templater.  But I don't
> really see where it goes wrong.  That is, unless `#if 0` causes the
> directives within the block to be ignored?

Well, the problematic function is:

numpy/core/src/multiarray/einsum_sumprod.c.src: In function
‘longdouble_sum_of_products_contig_three’:

So one should see a line directives in the function body that cause it ends
before it begins.

  parent reply	other threads:[~2021-06-10 14:40 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
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 [this message]
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-dLc7dtchIu@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).