diff options
| author | kelefth <konstantinos.eleftheriou@vrull.eu> | 2025-03-13 15:42:48 +0100 |
|---|---|---|
| committer | Philipp Tomsich <philipp.tomsich@vrull.eu> | 2025-04-18 10:31:40 +0200 |
| commit | 19af15ba7ad041b58b7926775cce81be9f5ec013 (patch) | |
| tree | 535196f07a5cad32826b409e075001f024423bdb /libjava/classpath/lib | |
| parent | dd982198656d914a4958bf86356a4c996c728b9d (diff) | |
| download | gcc-19af15ba7ad041b58b7926775cce81be9f5ec013.zip gcc-19af15ba7ad041b58b7926775cce81be9f5ec013.tar.gz gcc-19af15ba7ad041b58b7926775cce81be9f5ec013.tar.bz2 | |
doc: Clarify REG_EH_REGION note usage
The documentation for the REG_EH_REGION could easily be read
(especially by non-native speakers) to indicate that it should be
attached to insn at the destination of an excpetion edge. Despite the
original text saying that the note "specifies the destination," it is
actually always attached to the source instruction.
This updates the documentation to make it clear that the REG_EH_REGION
note is always attached to instructions originating an exception edge
and that the value of the note specifies where the exception edge
leads to.
Co-Developed-by: Philipp Tomsich <philipp.tomsich@vrull.eu>
gcc/ChangeLog:
* doc/cfg.texi: Update the exception handling section for the
REG_EH_REGION notes to make it clear that the note is attached
to the instruction throwing the exception.
Diffstat (limited to 'libjava/classpath/lib')
0 files changed, 0 insertions, 0 deletions