Re: Disappeared flag: -maes on -march=ivybridge, present in -march=native

On Mon, 29 Jul 2019, Kevin Weidemann wrote: I have recently randomly discovered the fact, that building with `-march=ivybridge` does not necessarily produce the same output as `-march=native` on an Intel Core i7 3770K (Ivy Bridge). Nothing so surprising there. Not all Ivy Bridge processors ar

[gcc 10-20190728] internal compiler error: in speculative_call_info, at cgraph.c:1114

Hi, While compiling gcc-10-20190728 snapshot: src/gcc-10-20190728/gcc/tree-ssa-sccvn.c:7323:1: internal compiler error: in speculative_call_info, at cgraph.c:1114 7323 | } | ^ 0x5d34b9 cgraph_edge::speculative_call_info(cgraph_edge*&, cgraph_edge*&, ipa_ref*&) /home/

Disappeared flag: -maes on -march=ivybridge, present in -march=native

Hello everyone, I have recently randomly discovered the fact, that building with `-march=ivybridge` does not necessarily produce the same output as `-march=native` on an Intel Core i7 3770K (Ivy Bridge). In particular, `-march=native` sets `-maes` whilst `-march=ivybridge` does not. After

gcc-10-20190728 is now available

Snapshot gcc-10-20190728 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/10-20190728/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 10 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision