public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tk at giga dot or.at" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/94479] New: NetBSD: internal compiler error: in recompute_tree_invariant_for_addr_expr
Date: Fri, 03 Apr 2020 19:29:05 +0000	[thread overview]
Message-ID: <bug-94479-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 94479
           Summary: NetBSD: internal compiler error: in
                    recompute_tree_invariant_for_addr_expr
           Product: gcc
           Version: 9.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: tk at giga dot or.at
  Target Milestone: ---

When compiling git-2.26.0 with gcc 8.3.0, 8.4.0, or 9.3.0 on NetBSD/amd64 with
-fstack-check, I see (output from 8.4.0):


builtin/rebase.c: In function 'cmd_rebase__interactive':
builtin/rebase.c:473:41: internal compiler error: in
recompute_tree_invariant_for_addr_expr, at tree.c:4487
   { OPTION_CALLBACK, 'k', "keep-empty", &options, NULL,
                                         ^~~~~~~~

I used creduce to get a minimal test case, save the following to rebase.i and
run:
# gcc -o rebase.o -c -fstack-check rebase.i

---- begin ----
int a;
struct b {
  char c;
  void *d;  
};
struct b e() {
  struct b f[] = {{}, "", f, a};
}
---- end ----

I tried running this in 8.3.0 and 9.3.0 on https://godbolt.org/ (where I had to
add -fpermissive for it to compile) but it doesn't seem to trigger the problem
there. So perhaps it's fine on Linux.

             reply	other threads:[~2020-04-03 19:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03 19:29 tk at giga dot or.at [this message]
2020-04-06  6:35 ` [Bug target/94479] " rguenth at gcc dot gnu.org
2020-04-06  6:40 ` tk at giga dot or.at
2020-04-06 17:12 ` tk at giga dot or.at
2020-04-07  6:11 ` rguenth at gcc dot gnu.org
2020-04-07  6:29 ` rguenth at gcc dot gnu.org
2020-04-07 13:26 ` tk at giga dot or.at
2020-04-07 14:29 ` rguenth at gcc dot gnu.org
2020-04-07 17:22 ` cvs-commit at gcc dot gnu.org
2020-04-07 17:23 ` rguenth at gcc dot gnu.org
2020-04-08  6:53 ` tk at giga dot or.at
2020-04-08  7:15 ` rguenther at suse dot de
2020-04-16 12:29 ` cvs-commit at gcc dot gnu.org
2021-03-17 10:20 ` cvs-commit at gcc dot gnu.org
2021-03-17 10:20 ` rguenth at gcc dot gnu.org
2021-09-11 14:29 ` 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-94479-4@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).