git
/
gcc
mirror of git://gcc.gnu.org/git/gcc.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[BRIGFE] allow controlling strict aliasing from cmd line 

From-SVN: r259948
This commit is contained in:
Pekka Jääskeläinen 2018-05-04 17:58:38 +00:00 committed by Pekka Jääskeläinen
parent 1c72513315
commit 77c42d456e
2 changed files with 14 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gcc/brig/ChangeLog
View File

@ -1,3 +1,8 @@
2018-05-04 Pekka Jääskeläinen <pekka.jaaskelainen@parmance.com>
* brig/brig-lang.c: Allow controlling strict aliasing from
cmd line.
2018-05-04 Pekka Jääskeläinen <pekka.jaaskelainen@parmance.com> 2018-05-04 Pekka Jääskeläinen <pekka.jaaskelainen@parmance.com>
* brig/brigfrontend/brig-code-entry-handler.cc: The modulo in * brig/brigfrontend/brig-code-entry-handler.cc: The modulo in

12
gcc/brig/brig-lang.c
View File

@ -167,9 +167,15 @@ brig_langhook_post_options (const char **pfilename ATTRIBUTE_UNUSED)
if (flag_excess_precision_cmdline == EXCESS_PRECISION_DEFAULT) if (flag_excess_precision_cmdline == EXCESS_PRECISION_DEFAULT)
flag_excess_precision_cmdline = EXCESS_PRECISION_STANDARD; flag_excess_precision_cmdline = EXCESS_PRECISION_STANDARD;
/* gccbrig casts pointers around like crazy, TBAA produces /* gccbrig casts pointers around like crazy, TBAA might produce broken
broken code if not force disabling it. */ code if not disabling it by default. Some PRM conformance tests such
flag_strict_aliasing = 0; as prm/core/memory/ordinary/ld/ld_u16 fail currently with strict
aliasing (to fix). It can be enabled from the command line for cases
that are known not to break the C style aliasing requirements. */
if (!global_options_set.x_flag_strict_aliasing)
flag_strict_aliasing = 0;
else
flag_strict_aliasing = global_options.x_flag_strict_aliasing;
/* Returning false means that the backend should be used. */ /* Returning false means that the backend should be used. */
return false; return false;