diff options
author | Andrew Pinski <quic_apinski@quicinc.com> | 2025-03-28 17:25:56 -0700 |
---|---|---|
committer | Andrew Pinski <quic_apinski@quicinc.com> | 2025-04-21 08:44:32 -0700 |
commit | 49926c2c657dd867f7329df6e250913fd1425475 (patch) | |
tree | a390a53dcc7d197d23274fa95c773f4dc67df228 /libgo/go/regexp/syntax/perl_groups.go | |
parent | d508d24282c6a8172be2abcb2223232f452b667f (diff) | |
download | gcc-49926c2c657dd867f7329df6e250913fd1425475.zip gcc-49926c2c657dd867f7329df6e250913fd1425475.tar.gz gcc-49926c2c657dd867f7329df6e250913fd1425475.tar.bz2 |
except: Don't use the cached value of the gcc_except_table section for comdat functions [PR119507]
This has been broken since GCC started to put the comdat functions' gcc_except_table into their
own section; r0-118218-g3e6011cfebedfb. What would happen is after a non-comdat function is processed,
the cached value would always be used even for comdat function. Instead we should create a new
section for comdat functions.
OK? Bootstrapped and tested on x86_64-linux-gnu.
PR middle-end/119507
gcc/ChangeLog:
* except.cc (switch_to_exception_section): Don't use the cached section if
the current function is in comdat.
gcc/testsuite/ChangeLog:
* g++.dg/eh/pr119507.C: New test.
Signed-off-by: Andrew Pinski <quic_apinski@quicinc.com>
Diffstat (limited to 'libgo/go/regexp/syntax/perl_groups.go')
0 files changed, 0 insertions, 0 deletions