public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/99324] [8/9/10/11 Regression] ICE in mark_addressable, at gimple-expr.c:918 since r6-314 Date: Tue, 02 Mar 2021 10:27:25 +0000 [thread overview] Message-ID: <bug-99324-4-qV1gqJNvtr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99324-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99324 --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #3) > Wouldn't it be better to remove the mark_addressable call from build_va_arg > and call {c,cxx}_mark_addressable in the callers instead. Sure, or make it a langhook so c-common code can call the "correct" mark_addresable (there's also c_common_mark_addressable_vec which might suggest that splitting out common c_common_mark_addressable from {c,cxx}_mark_addressable should be viable and use that). > That way we'd also e.g. diagnose invalid (on i686-linux): > register __builtin_va_list ap __asm ("%ebx"); > > void > foo (int a, ...) > { > __builtin_va_arg (ap, int); > }
next prev parent reply other threads:[~2021-03-02 10:27 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-01 17:05 [Bug c/99324] New: ICE in mark_addressable, at gimple-expr.c:918 gscfq@t-online.de 2021-03-02 7:42 ` [Bug c/99324] " rguenth at gcc dot gnu.org 2021-03-02 9:45 ` [Bug c/99324] [8/9/10/11 Regression] ICE in mark_addressable, at gimple-expr.c:918 since r6-314 jakub at gcc dot gnu.org 2021-03-02 10:02 ` jakub at gcc dot gnu.org 2021-03-02 10:27 ` rguenth at gcc dot gnu.org [this message] 2021-03-02 11:30 ` jakub at gcc dot gnu.org 2021-03-03 8:55 ` cvs-commit at gcc dot gnu.org 2021-03-03 8:58 ` [Bug c/99324] [8/9/10 " jakub at gcc dot gnu.org 2021-03-19 23:30 ` cvs-commit at gcc dot gnu.org 2021-03-20 8:09 ` [Bug c/99324] [8/9 " jakub at gcc dot gnu.org 2021-04-20 23:33 ` cvs-commit at gcc dot gnu.org 2021-04-22 16:51 ` cvs-commit at gcc dot gnu.org 2021-04-22 17:11 ` jakub 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-99324-4-qV1gqJNvtr@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: linkBe 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).