public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fredrik.hederstierna@securitas-direct.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/95152] internal compiler error: in get_or_create_mem_ref, at analyzer/region-model.cc:6938
Date: Sat, 16 May 2020 08:40:24 +0000 [thread overview]
Message-ID: <bug-95152-4-aMdyAXgQyy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95152-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95152
Fredrik Hederstierna <fredrik.hederstierna@securitas-direct.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fredrik.hederstierna@securi
| |tas-direct.com
--- Comment #2 from Fredrik Hederstierna <fredrik.hederstierna@securitas-direct.com> ---
I have had the same problem with arm-none-eabi-gcc (GCC) 10.1.0, using
-fanalyzer.
Compiling my_test.c ..
during IPA pass: analyzer
falcon_fota.c: In function 'my_verify.part.0':
falcon_fota.c:629:5: internal compiler error: in get_or_create_mem_ref, at
analyzer/region-model.cc:6938
629 | app_info_t *app_info = RAM_APP_INFO_POS;
| ^~~~~~~~~~~~~~~~~~~~~~~~~
Please submit a full bug report,
with preprocessed source if appropriate.
The pointer RAM_APP_INFO_POS is a quite special reference with address of
external variable, and adding constants to that value:
// example
extern void *_app_data_offs;
#define RAM_ADDRESS ((uint32_t)(0xC0000000))
#define APP_INFO_POS ((uint32_t)&_app_data_offs)
#define RAM_APP_INFO_POS (RAM_ADDRESS + APP_INFO_POS)
arm-eabi-gcc -v
Using built-in specs.
COLLECT_GCC=/opt/gcc/arm-none-eabi-toolchain-gcc-10.1.0-binutils-2.33.1-newlib-3.3.0-hardfloat/bin/arm-none-eabi-gcc
COLLECT_LTO_WRAPPER=/opt/gcc/arm-none-eabi-toolchain-gcc-10.1.0-binutils-2.33.1-newlib-3.3.0-hardfloat/libexec/gcc/arm-none-eabi/10.1.0/lto-wrapper
Target: arm-none-eabi
Configured with: ../../gcc-10.1.0/configure --enable-languages=c,c++
--target=arm-none-eabi
--prefix=/opt/gcc/arm-none-eabi-toolchain-gcc-10.1.0-binutils-2.33.1-newlib-3.3.0-hardfloat
--with-gnu-as --with-gnu-ld --with-newlib --with-system-zlib
--with-endian=little --disable-interwork --with-mode=thumb --with-abi=aapcs
--with-cpu=cortex-m4 --with-float=hard --with-fpu=fpv4-sp-d16 --disable-nls
--disable-libssp --enable-multilib
Thread model: single
Supported LTO compression algorithms: zlib
gcc version 10.1.0 (GCC)
next prev parent reply other threads:[~2020-05-16 8:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 12:45 [Bug analyzer/95152] New: " pieter+gcc-bugzilla at plexis dot eu
2020-05-15 13:26 ` [Bug analyzer/95152] " marxin at gcc dot gnu.org
2020-05-16 8:40 ` fredrik.hederstierna@securitas-direct.com [this message]
2020-05-18 5:40 ` [Bug analyzer/95152] ICE in get_or_create_mem_ref, at analyzer/region-model.cc:6938 since r10-5950-g757bf1dff5e8cee3 marxin at gcc dot gnu.org
2020-05-18 6:52 ` fredrik.hederstierna@securitas-direct.com
2020-06-02 6:37 ` yagi.uwu at gmail dot com
2020-08-21 1:16 ` cvs-commit at gcc dot gnu.org
2020-08-21 1:21 ` dmalcolm 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-95152-4-aMdyAXgQyy@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).