diff options
| author | Thomas Schwinge <tschwinge@baylibre.com> | 2025-05-26 13:31:54 +0200 |
|---|---|---|
| committer | Thomas Schwinge <tschwinge@baylibre.com> | 2025-06-04 19:47:22 +0200 |
| commit | d283eba8b886921424ef86ce1804ecfcbc49b8fc (patch) | |
| tree | 71a900313da96c3e2f788f498c2f89e299b69596 /gcc/dwarf2ctf.cc | |
| parent | 3f67be6a45634add47d777dcd7a5f95ed313adee (diff) | |
| download | gcc-d283eba8b886921424ef86ce1804ecfcbc49b8fc.zip gcc-d283eba8b886921424ef86ce1804ecfcbc49b8fc.tar.gz gcc-d283eba8b886921424ef86ce1804ecfcbc49b8fc.tar.bz2 | |
Avoid SIGSEGV in nvptx 'mkoffload' for voluminous PTX code
In commit 50be486dff4ea2676ed022e9524ef190b92ae2b1
"nvptx: libgomp+mkoffload.cc: Prepare for reverse offload fn lookup", some
additional tracking of the PTX code was added, and this assumes that
potentially every single character of PTX code needs to be tracked as a new
chunk of PTX code. That's problematic if we're dealing with voluminous PTX
code (for example, non-trivial C++ code), and the 'file_idx' 'alloca'tion then
causes stack overflow. For example:
FAIL: libgomp.c++/target-std__valarray-1.C (test for excess errors)
UNRESOLVED: libgomp.c++/target-std__valarray-1.C compilation failed to produce executable
lto-wrapper: fatal error: [...]/build-gcc/gcc//accel/nvptx-none/mkoffload terminated with signal 11 [Segmentation fault], core dumped
gcc/
* config/nvptx/mkoffload.cc (process): Use an 'auto_vec' for
'file_idx'.
(cherry picked from commit 01044e0ee27093a3990996578b15f6ab69ed3395)
Diffstat (limited to 'gcc/dwarf2ctf.cc')
0 files changed, 0 insertions, 0 deletions