public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dflogeras2 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/106068] New: Infinite loop generated with -mcpu=cortex-m7 and -O2 Date: Thu, 23 Jun 2022 19:36:49 +0000 [thread overview] Message-ID: <bug-106068-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106068 Bug ID: 106068 Summary: Infinite loop generated with -mcpu=cortex-m7 and -O2 Product: gcc Version: 10.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: dflogeras2 at gmail dot com Target Milestone: --- Created attachment 53197 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53197&action=edit Preprocessed src to reproduce bug We hit this suspected bug compiling an older firmware after recently upgrading to a more recent version of GCC. It can be triggered by 11.3.0, while the old 5.4.x version did not produce the infinite loop. The code snippet is from a quite old version of LWIP (stripped down to the minimal). It appears to not be exiting the loop on the second condition (n<2). The exact command I used to generate the .i is as follows: arm-none-eabi-gcc -mcpu=cortex-m7 src/core/dhcp.c -c -save-temps -g -O2 GCC that it definitely fails on is as follows: arm-none-eabi-gcc -v Using built-in specs. COLLECT_GCC=arm-none-eabi-gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/arm-none-eabi/11.3.0/lto-wrapper Target: arm-none-eabi Configured with: /var/tmp/notmpfs/portage/cross-arm-none-eabi/gcc-11.3.0/work/gcc-11.3.0/configure --host=x86_64-pc-linux-gnu --target=arm-none-eabi --build=x86_64-pc-linux-gnu --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/arm-none-eabi/gcc-bin/11.3.0 --includedir=/usr/lib/gcc/arm-none-eabi/11.3.0/include --datadir=/usr/share/gcc-data/arm-none-eabi/11.3.0 --mandir=/usr/share/gcc-data/arm-none-eabi/11.3.0/man --infodir=/usr/share/gcc-data/arm-none-eabi/11.3.0/info --with-gxx-include-dir=/usr/lib/gcc/arm-none-eabi/11.3.0/include/g++-v11 --with-python-dir=/share/gcc-data/arm-none-eabi/11.3.0/python --enable-languages=c,c++ --enable-obsolete --enable-secureplt --disable-werror --with-system-zlib --enable-nls --without-included-gettext --disable-libunwind-exceptions --enable-checking=release --with-bugurl=https://bugs.gentoo.org/ --with-pkgversion='Gentoo 11.3.0 p4' --disable-esp --enable-libstdcxx-time --disable-libstdcxx-pch --enable-poison-system-directories --disable-libstdcxx-time --with-sysroot=/usr/arm-none-eabi --disable-bootstrap --with-newlib --enable-multilib --disable-fixed-point --disable-libgomp --disable-libssp --disable-libada --disable-cet --disable-systemtap --disable-valgrind-annotations --disable-vtable-verify --disable-libvtv --without-zstd --enable-lto --without-isl --disable-libsanitizer --disable-default-pie --enable-default-ssp --with-multilib-list=rmprofile Thread model: single Supported LTO compression algorithms: zlib gcc version 11.3.0 (Gentoo 11.3.0 p4)
next reply other threads:[~2022-06-23 19:36 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-23 19:36 dflogeras2 at gmail dot com [this message] 2022-06-23 19:43 ` [Bug target/106068] " pinskia at gcc dot gnu.org 2022-06-23 19:53 ` dflogeras2 at gmail dot com 2022-06-23 19:56 ` pinskia 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-106068-4@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).