public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "julien.staub at se dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/108340] New: compiler segfault
Date: Mon, 09 Jan 2023 11:56:29 +0000 [thread overview]
Message-ID: <bug-108340-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108340
Bug ID: 108340
Summary: compiler segfault
Product: gcc
Version: 12.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: julien.staub at se dot com
Target Milestone: ---
Created attachment 54216
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54216&action=edit
minimal file to reproduce
To reproduce :
1. Downloaded arm-gnu-toolchain-12.2.rel1-mingw-w64-i686-arm-none-eabi.zip from
https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads
2. In attached zip, modify and run compilerBug.bat (will just compile 1 faulty
file known to work)
3. observe segmentation fault in compiler
Actual Results: What happened after performing the above steps.
```
C:\FW>"C:\GIT\FW_Toolchain\GNU Tools ARM
Embedded\12.2.rel1\bin\arm-none-eabi-gcc.exe" -DSTM32U575xx=1
-IC:/FW/minimalInc -O3 -DNDEBUG -freport-bug -mcpu=cortex-m33 -mthumb
-mfpu=fpv5-sp-d16 -mfloat-abi=hard --specs=nano.specs -ffunction-sections
-fdata-sections -fno-builtin -Wall -Wfatal-errors -O3 -std=gnu17 -o
stm32u5xx_hal_dma_ex.c.obj -c C:/FW/minimalInc/stm32u5xx_hal_dma_ex.c
during GIMPLE pass: evrp
C:/FW/minimalInc/stm32u5xx_hal_dma_ex.c: In function
'HAL_DMAEx_List_ReplaceNode_Head':
C:/FW/minimalInc/stm32u5xx_hal_dma_ex.c:4689:1: internal compiler error:
Segmentation fault
4689 | }
| ^
Please submit a full bug report, with preprocessed source.
See <https://bugs.linaro.org/> for instructions.
The bug is not reproducible, so it is likely a hardware or OS problem.
```
It's possible to reproduce issue with only godbolt :
https://godbolt.org/z/oG8rGfG4E
and GCC 11.x to 12.2 seem affected. -O0 will not show the bug.
I also opened the bug on Linaro for arm-none-aebi-gcc build but it seems this
is a GCC issue and I did not find it bug list.
https://bugs.linaro.org/show_bug.cgi?id=5924
next reply other threads:[~2023-01-09 11:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 11:56 julien.staub at se dot com [this message]
2023-01-09 12:15 ` [Bug c/108340] " julien.staub at se dot com
2023-01-09 12:24 ` marxin at gcc dot gnu.org
2023-01-09 12:33 ` marxin at gcc dot gnu.org
2023-01-09 13:46 ` julien.staub at se dot com
2023-01-09 14:53 ` 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-108340-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: 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).