> We noticed a difference in the code generated for aarch64 gcc 7.2
> hosted in Linux vs mingw. AFIK, we are supposed to produce the same
> output.
Try maybe to compare the automata generated on the hosts, are they identical?
--
Eric Botcazou
On Wed, 4 Jul 2018, Kugan Vivekanandarajah wrote:
> We noticed a difference in the code generated for aarch64 gcc 7.2
> hosted in Linux vs mingw. AFIK, we are supposed to produce the same
> output.
>
> For the testacse we have (quite large and I am trying to reduce), the
> difference comes from sc
On Tue, Jul 3, 2018 at 9:09 PM Jeff Law wrote:
>
> On 07/03/2018 11:55 AM, Michael Ploujnikov wrote:
> > On 2018-07-03 12:46 PM, Richard Biener wrote:
> >> On July 3, 2018 4:56:57 PM GMT+02:00, Michael Ploujnikov
> >> wrote:
> >>> On 2018-06-20 04:23 AM, Richard Biener wrote:
> On Wed, Jun
On 06/19/2018 04:37 AM, Thomas Schwinge wrote:
Hi!
In case that you have not yet found it:
On Mon, 11 Jun 2018 12:19:23 -0600, Martin Sebor wrote:
I've been noticing a number of failures in LTO (and some other)
tests in my x86_64-builds most of which don't appear in results
reported on gcc-te
Snapshot gcc-6-20180704 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/6-20180704/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 6 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-6
Hello.
The source in the attachment can not be compiled, because there is a
variable in the lambda-introducer does not have a copy-constructor, but have a
move-constructor. When a function object constructed by a lambda-expression
like this, the compiler will report this error. And I have tr
在 2018/7/5 9:14, snow_xmas 写道:
Hello.
The source in the attachment can not be compiled, because there is a
variable in the lambda-introducer does not have a copy-constructor, but have a
move-constructor. When a function object constructed by a lambda-expression
like this, the compiler wil
In the function emit_side_effect_warnings, I find its inputs are "location_t
loc" and "tree expr".
And, there is a function warn_if_unused_value called by
emit_side_effect_warnings:
emit_side_effect_warnings(location_t loc, tree expr){ ...
else
warn_if_unused_value(expr,loc)
}
To
