public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/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 17:35:04 +0000	[thread overview]
Message-ID: <bug-100734-4-mv70OhEaAk@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 #5 from John David Anglin <danglin at gcc dot gnu.org> ---
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 ();
(gdb) bt
#0  attr_access::from_mode_char (
    c=<error reading variable: Cannot access memory at address 0x0>)
    at ../../gcc/gcc/attribs.h:304
#1  0x4000000000a8311c in init_attr_rdwr_indices (rwm=0x800003fffdff14e0,
    attrs=0x800003fffdf1b9b0) at ../../gcc/gcc/attribs.c:2146
#2  0x4000000000d1e554 in warn_parm_array_mismatch (origloc=2147484671,
    fndecl=0x800003fffdf1b9b0, newparms=0x7ae4b8)
    at ../../gcc/gcc/c-family/c-warn.c:3369
#3  0x4000000000b5ebc0 in c_parser_declaration_or_fndef (
    parser=0x800003fffdff14e0, fndef_ok=128, static_assert_ok=false,
    empty_ok=true, nested=false, start_attr_ok=false,
    objc_foreach_object_declaration=0x4000000000887f48
<copy_list(tree_node*)::__FUNCTION__>, omp_declare_simd_clauses=...,
have_attrs=false,
    attrs=0x800003fffdf1d700,
    oacc_routine_data=0x4000000002f7501f <fndecl_built_in_p(tree_node
const*)+92>, fallthru_attr_p=0x800003fffdff17a0) at
../../gcc/gcc/c/c-parser.c:2342
#4  0x4000000000b5cb98 in c_parser_external_declaration (
    parser=0x800003fffdff14e0) at ../../gcc/gcc/c/c-parser.c:1777
#5  0x4000000000b5c240 in c_parser_translation_unit (parser=0x800003fffdff14e0)
    at ../../gcc/gcc/c/c-parser.c:1650
#6  0x4000000000bc644c in c_parse_file () at ../../gcc/gcc/c/c-parser.c:21994
#7  0x4000000000cafd10 in c_common_parse_file ()
    at ../../gcc/gcc/c-family/c-opts.c:1219
#8  0x40000000017db87c in compile_file () at ../../gcc/gcc/toplev.c:457
#9  0x40000000017e26e8 in do_compile () at ../../gcc/gcc/toplev.c:2203
#10 0x40000000017e2e68 in toplev::main (this=0x800003fffdff14e0,
    argc=-2147482625, argv=0x7ae4b8) at ../../gcc/gcc/toplev.c:2342
#11 0x4000000002abbee4 in main (argc=-2147482625, argv=0x800003fffdf1b9b0)
    at ../../gcc/gcc/main.c:39
(gdb) frame 1
#1  0x4000000000a8311c in init_attr_rdwr_indices (rwm=0x800003fffdff14e0,
    attrs=0x800003fffdf1b9b0) at ../../gcc/gcc/attribs.c:2146
2146              acc.mode = acc.from_mode_char (*m);
(gdb) p *m
$2 = 0 '\000'

  parent reply	other threads:[~2021-05-25 17:35 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 [this message]
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
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-mv70OhEaAk@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).