diff options
author | Sam James <sam@gentoo.org> | 2025-03-24 04:32:47 +0000 |
---|---|---|
committer | Sam James <sam@gentoo.org> | 2025-04-17 16:19:44 +0100 |
commit | 7c47badcdc8625ea53aed275be96c32bc78db25b (patch) | |
tree | 40adea7a2ee89d42ed626c8b204b77694bd3c305 /libjava/classpath | |
parent | c237297ee596545552f48ec9582d7d16703d8949 (diff) | |
download | gcc-7c47badcdc8625ea53aed275be96c32bc78db25b.zip gcc-7c47badcdc8625ea53aed275be96c32bc78db25b.tar.gz gcc-7c47badcdc8625ea53aed275be96c32bc78db25b.tar.bz2 |
doc: say "compatible types" for -fstrict-aliasing
Include the term used in the standard to ease further research for users,
and while at it, rephrase the description of the rule entirely using
Alexander Monakov's suggestion: it was previously wrong (and imprecise) as
"the same address" may well be re-used later on, and the issue is the
access via an expression of the wrong type.
gcc/ChangeLog:
* doc/invoke.texi: Use "compatible types" term. Rephrase to be
more precise (and correct).
Diffstat (limited to 'libjava/classpath')
0 files changed, 0 insertions, 0 deletions