public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/99641] [11 Regression] opt30.adb, opt49.adb and loop_optimization3.adb fail to build at m32 Date: Fri, 19 Mar 2021 09:42:39 +0000 [thread overview] Message-ID: <bug-99641-4-BOcml02yZ1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99641-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99641 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Eric Botcazou <ebotcazou@gcc.gnu.org>: https://gcc.gnu.org/g:b980edba506442c846cc779243ceeffd13065740 commit r11-7729-gb980edba506442c846cc779243ceeffd13065740 Author: Eric Botcazou <ebotcazou@adacore.com> Date: Fri Mar 19 09:21:11 2021 +0100 Fix segfault during encoding of CONSTRUCTORs The segfault occurs in native_encode_initializer when it is encoding the CONSTRUCTOR for an array whose lower bound is negative (it's OK in Ada). The computation of the current position is done in HOST_WIDE_INT and this does not work for arrays whose original range has a negative lower bound and a positive upper bound; the computation must be done in sizetype instead so that it may wrap around. gcc/ PR middle-end/99641 * fold-const.c (native_encode_initializer) <CONSTRUCTOR>: For an array type, do the computation of the current position in sizetype.
next prev parent reply other threads:[~2021-03-19 9:42 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-18 9:37 [Bug ada/99641] New: " iains at gcc dot gnu.org 2021-03-18 9:39 ` [Bug ada/99641] " iains at gcc dot gnu.org 2021-03-18 9:58 ` ebotcazou at gcc dot gnu.org 2021-03-18 10:32 ` [Bug middle-end/99641] " ebotcazou at gcc dot gnu.org 2021-03-19 9:42 ` cvs-commit at gcc dot gnu.org [this message] 2021-03-19 9:46 ` cvs-commit at gcc dot gnu.org 2021-03-19 9:47 ` ebotcazou 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-99641-4-BOcml02yZ1@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).