public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/100734] [12 Regression] /test/gnu/gcc/objdir/gcc/include-fixed/stdlib.h:291:8: internal compiler error: in from_mode_char, at attribs.h:304
Date: Tue, 25 May 2021 19:13:53 +0000 [thread overview]
Message-ID: <bug-100734-4-EaGx3Y4vDO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100734-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100734
--- Comment #9 from Martin Sebor <msebor at gcc dot gnu.org> ---
(In reply to John David Anglin from comment #5)
> Breakpoint 1, attr_access::from_mode_char (
> c=<error reading variable: Cannot access memory at address 0x0>)
> at ../../gcc/gcc/attribs.h:304
> 304 gcc_unreachable ();
This error says that &c is null. c comes from the code below:
#1 0x4000000000a8311c in init_attr_rdwr_indices (rwm=0x800003fffdff14e0,
attrs=0x800003fffdf1b9b0) at ../../gcc/gcc/attribs.c:2146
mode = TREE_VALUE (mode);
if (TREE_CODE (mode) != STRING_CST)
continue;
gcc_assert (TREE_CODE (mode) == STRING_CST);
for (const char *m = TREE_STRING_POINTER (mode); *m; )
Either TREE_STRING_POINTER (mode) is null or mode is set to null after one of
the calls to strtoul() later in the function.
next prev parent reply other threads:[~2021-05-25 19:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-23 19:38 [Bug bootstrap/100734] New: " danglin at gcc dot gnu.org
2021-05-24 7:19 ` [Bug target/100734] [12 Regression] " pinskia at gcc dot gnu.org
2021-05-24 7:25 ` pinskia at gcc dot gnu.org
2021-05-24 11:28 ` dave.anglin at bell dot net
2021-05-25 8:26 ` rguenth at gcc dot gnu.org
2021-05-25 13:55 ` danglin at gcc dot gnu.org
2021-05-25 17:35 ` danglin at gcc dot gnu.org
2021-05-25 18:35 ` [Bug middle-end/100734] " pinskia at gcc dot gnu.org
2021-05-25 18:37 ` pinskia at gcc dot gnu.org
2021-05-25 19:04 ` msebor at gcc dot gnu.org
2021-05-25 19:13 ` msebor at gcc dot gnu.org [this message]
2021-05-26 19:32 ` dave.anglin at bell dot net
2021-05-28 17:35 ` dave.anglin at bell dot net
2021-06-05 15:10 ` [Bug target/100734] " danglin at gcc dot gnu.org
2021-06-05 15:49 ` cvs-commit at gcc dot gnu.org
2021-06-05 16:09 ` danglin at gcc dot gnu.org
2021-10-01 17:19 ` cvs-commit 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-100734-4-EaGx3Y4vDO@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).