Hi,
I would like to ping this patch:
https://gcc.gnu.org/ml/gcc-patches/2017-11/msg01451.html
While the patch touches quite a few places, it is mostly reshuffling
and generalizing existing code. It also includes tests for the new
functionality. Seeing that there is a lot of interest[1] in reprod
On 11/22/2017 10:46 AM, Richard Sandiford wrote:
> One of the effects of:
>
>https://gcc.gnu.org/ml/gcc-patches/2017-10/msg02066.html
>
> is that we now emit:
>
>(set (hard-frame-pointer) (stack-pointer))
>
> instead of the previous non-canonical:
>
>(set (hard-frame-pointer) (plus
On 23/11/17 22:40 +, Jonathan Wakely wrote:
C++17 added the [[nodiscard]] attribute, similar to GCC's
warn_unused_result. The C++2a draft requires it to be used in several
places. This patch adds it where required on components which are new
to C++17, which are still experimental and so I'm c
On 22 November 2017 at 12:26, Kyrill Tkachov
wrote:
> Hi Tamar,
>
> On 06/11/17 16:53, Tamar Christina wrote:
>>
>> Hi All,
>>
>> This patch adds the NEON intrinsics for Dot product.
>>
>> Dot product is available from ARMv8.2-a and onwards.
>>
>> Regtested on arm-none-eabi, armeb-none-eabi,
>> a
This fixes a small oversight in gigi, which can lead to an inconsistency
between type variants for the mode when packed array types are involved.
Tested on x86-64/Linux, applied on the mainline.
2017-11-23 Eric Botcazou
PR ada/83091
* gcc-interface/decl.c (gnat_to_gnu_entity
On 23/11/17 22:40 +, Jonathan Wakely wrote:
C++17 added the [[nodiscard]] attribute, similar to GCC's
warn_unused_result. The C++2a draft requires it to be used in several
places. This patch adds it where required on components which are new
to C++17, which are still experimental and so I'm c
On Thu, 23 Nov 2017, Kirill Yukhin wrote:
Hello, Julia!
On 24 Oct 08:25, Koval, Julia wrote:
Hi,
This patch enables VPCOMPRESSB[W] instruction. The doc for isaset and
instruction:
https://software.intel.com/sites/default/files/managed/c5/15/architecture-instruction-set-extensions-programming-
C++17 added the [[nodiscard]] attribute, similar to GCC's
warn_unused_result. The C++2a draft requires it to be used in several
places. This patch adds it where required on components which are new
to C++17, which are still experimental and so I'm changing them in
stage 3.
* include/bits/
On 23 November 2017 at 09:22, Richard Biener wrote:
> On Wed, 22 Nov 2017, Christophe Lyon wrote:
>
>> On 22 November 2017 at 09:44, Richard Biener wrote:
>> >
>> > The following fixes if-conversion to free SCEV/niter estimates because
>> > it DCEs stmts.
>> >
>> > Bootstrapped and tested on x86_
On Thu, Nov 23, 2017 at 11:54 AM, Tom de Vries wrote:
> Hi,
>
> this patch wraps CLASS_TABLE_HASH in "do {} while (0)". This allows the
> macro to be used in if-then-elses without curly braces.
>
> Build libobcj for x86_64.
>
> Committed as obvious.
Yes this is ok.
Thanks,
Andrew
>
> Thanks,
>
Agustín reported this bug in std::negation, so we need to fix our
underlying __not_<> template to meet the C++17 requirements for
std::negation.
PR libstdc++/83134
* include/std/type_traits (__not_): Explicitly convert to bool.
* testsuite/20_util/declval/requirements/1_ne
Gentle reminder for this patch.
I looked when the constructor got unused and I think it is back in June
2015 in git commit:
commit debb6aabb771ed02cb7256a7719555e5fbd7d3f7
Author: redi
Date: Wed Jun 17 17:45:45 2015 +
* include/bits/forward_list.h
(_Fwd_list_base(const
Hello, Julia!
On 24 Oct 08:35, Koval, Julia wrote:
> Hi,
> This patch enables VPEXPANDB[W] instruction. The doc for isaset and
> instruction:
> https://software.intel.com/sites/default/files/managed/c5/15/architecture-instruction-set-extensions-programming-reference.pdf
>
> Ok for trunk?
Your pa
Hi!
With -mno-altivec -mno-vsx -mno-fold-gimple we error on __builtin_vec*
builtins used when corresponding ISA is not enabled.
When folding gimple, in some cases we get away with it (e.g. when folding
the builtin to PLUS_EXPR on the generic vectors), because
tree-vect-generic.c lowers those into
Hello, Julia!
On 24 Oct 08:25, Koval, Julia wrote:
> Hi,
> This patch enables VPCOMPRESSB[W] instruction. The doc for isaset and
> instruction:
> https://software.intel.com/sites/default/files/managed/c5/15/architecture-instruction-set-extensions-programming-reference.pdf
>
> Ok for trunk?
Your
Hi!
>From my reading of the PR and looking around, I believe the reason
ubsan ICEs on mingw hosts is that it is the only host that redefines
HOST_LONG_LONG_FORMAT to "I64" instead of the usual "ll", but "%I64"
is nothing pp_format can handle, and indeed this spot in ubsan.c is
the only place that
Hi!
My PR81258 fix actually rejects even valid cases.
The standard says that:
"The initializer shall be of the form “= assignment-expression”, of the form
“{ assignment-expression }”, or of the form “( assignment-expression )”
Now, if the form is = assigment-expression, we can e.g. in templates en
Hi!
As mentioned on IRC, we can actually now use ERF_RETURN*_ARG* to find out
what functions are pass through (except for __builtin_assume_aligned, which
is pass through but we never want to propagate the arg to the result early, as
the result contains additional information, so it isn't RET1).
W
Hi!
The -Wreturn-type warning on declare-simd-1.C shows we were actually
misparsing it with -fopenmp, e.g.
if (1)
#pragma omp declare simd
extern float foo (float);
n++;
was actually parsed as
if (1)
{
#pragma omp declare simd
extern float foo (float);
n++;
Hi!
Unlike C++, C doesn't allow function declarations inside of if/while/for
body without {}s around, or after a label, while with #pragma omp declare simd
in between and -fopenmp it would happily accept it. That is wrong, the
presence/absence of OpenMP pragmas shouldn't change parsing that way.
On Fri, Sep 01, 2017 at 03:47:10PM +0200, dbroemmel wrote:
> > If you really need a testcase, it would be enough to do something like:
> > use omp_lib
> > !$omp parallel num_threads(2)
> > int2 = omp_get_thread_num ()
> > !$omp barrier
> > if (int2 != omp_get_thread_num ()) call abort
> >
Hi!
In powerpc64{,le}-linux bootstraps I've discovered 4 spots missing
-Wno-return-type (the warning is in the included header and the tests are
for code generation, so I'd prefer not to change the code).
Committed to trunk as obvious.
2017-11-23 Jakub Jelinek
* g++.dg/pr65240-1.C: A
Hi,
this patch wraps RETURN_NULL_IF_FAIL_NONNULL_NUMERIC_TYPE in
JIT_{BEGIN,END}_STMT. This allows the macro to be used in if-then-elses
without curly braces.
Tested by doing x86_64 build with jitfe enabled.
Committed as obvious.
Thanks,
- Tom
[libgccjit] Wrap RETURN_NULL_IF_FAIL_NONNULL_NU
Hi,
this patch wraps the sh version of ASM_OUTPUT_ADDR_VEC_ELT in "do {}
while (0)". This allows the macro to be used in if-then-elses without
curly braces.
Build for sh.
Committed as obvious.
Thanks,
- Tom
[sh] Wrap ASM_OUTPUT_ADDR_VEC_ELT in do {} while (0)
2017-11-23 Tom de Vries
Hi,
this patch wraps CLASS_TABLE_HASH in "do {} while (0)". This allows the
macro to be used in if-then-elses without curly braces.
Build libobcj for x86_64.
Committed as obvious.
Thanks,
- Tom
[libobjc] Wrap CLASS_TABLE_HASH in do {} while (0)
2017-11-23 Tom de Vries
* class.c (CLASS_
Hi,
This removes a semicolon after the ft32 version of
ASM_OUTPUT_ADDR_VEC_ELT. This allows the macro to be used in
if-then-elses without curly braces.
Build for ft32.
Committed as obvious.
Thanks,
- Tom
[ft32] Remove semicolon after ASM_OUTPUT_ADDR_VEC_ELT
2017-11-23 Tom de Vries
* c
Hi!
On Mon, Nov 20, 2017 at 04:06:54PM -0600, Will Schmidt wrote:
> Add additional scan-assembler entries for those tests with
> simple variations in codegen. (for power9, versus power8, etc).
>
>
> 2017-11-20 Will Schmidt
>
> [testsuite]
>
> * fold-vec-abs-c
Hi Will,
On Mon, Nov 20, 2017 at 04:05:55PM -0600, Will Schmidt wrote:
> Update the scan-assembler stanza to include those instructions
> generated for a power9 target.
>
> 2017-11-20 Will Schmidt
>
> [testsuite]
>
> * fold-vec-ld-char.c: Add lxv insn to expec
On Tue, 21 Nov 2017, Gerald Pfeifer wrote:
> /scratch/tmp/gerald/GCC-HEAD/gcc/print-rtl.c:982:1: error: explicit
> instantiation cannot have a storage class
> DEFINE_DEBUG_VEC (rtx_def *)
> ^
> /scratch/tmp/gerald/GCC-HEAD/gcc/vec.h:456:24: note: expanded from macro
> 'DEFINE_DEBUG_VEC'
> templ
On 23 November 2017 at 10:01, Kyrill Tkachov
wrote:
>
> Thanks, these are ok for trunk.
> They were originally posted way before stage 3 and this is just a rework,
> so it's acceptable at this stage as far as I'm concerned.
Thanks. Committed to trunk as r255111.
On 15 September 2017 at 17:57, Kyrill Tkachov
wrote:
>
> Thanks, this is ok once the prerequisites are sorted.
Patch 1 was abandoned, and a later version of patch 2 has been
committed, so this was applied to trunk as r255112.
Hi!
On Mon, Nov 20, 2017 at 04:04:18PM -0600, Will Schmidt wrote:
> Update the scan-assembler stanza to include those instructions
> generated for a power9 target.
>
> 2017-11-20 Will Schmidt
>
> [testsuite]
> * fold-vec-splat-8.c : Add vspltisb to expected output.
On Mon, Nov 20, 2017 at 02:16:59PM -0600, Will Schmidt wrote:
> > > --- a/gcc/testsuite/gcc.target/powerpc/fold-vec-abs-int-fwrapv.c
> > > +++ b/gcc/testsuite/gcc.target/powerpc/fold-vec-abs-int-fwrapv.c
> > > @@ -1,11 +1,11 @@
> > > /* Verify that overloaded built-ins for vec_abs with int
> > >
Hi Janne,
However, to continue my nitpicking (sorry!), it seems that in many
cases compare_fcn still takes an integer length argument. Could you
make that gfc_charlen_type as well? Or maybe size_t, since the
argument is passed straight to memcmp{_char4} anyway? Please consider
such a patch pre-a
Hi!
On Thu, Nov 23, 2017 at 10:26:28AM +0100, Jakub Jelinek wrote:
> While looking at this function, I found so many formatting issues
> (indentation and spacing) that I've decided to post a patch. As an
> additional cleanup, I've moved the temp and g declarations to the top of
> the function, so
On 11/22/2017 01:38 AM, Koval, Julia wrote:
> Hi,
>
>> So it's not important, but the patch doesn't have the removal of the
>> cilk+ testsuite or runtime. BUt again, it's not a big deal, I can guess
>> what that part of the patch looks like.
>
> I used Jakub's suggestion in
> https://gcc.gnu.or
Jakub Jelinek writes:
> On Thu, Nov 23, 2017 at 02:43:32PM +0100, Michael Matz wrote:
>> > If it's a VEC_PERM_EXPR then it'll be a new form of VEC_PERM_EXPR.
>>
>> No, it'd be a VEC_PERM_EXPR where the magic mask is generated by a new
>> EXPR type, instead of being a mere constant.
>
> Or an int
On Thu, 2017-11-23 at 14:33 +0100, Jakub Jelinek wrote:
> On Thu, Nov 23, 2017 at 02:13:57PM +0100, Mark Wielaard wrote:
> > * dwarf2out.c (init_sections_and_labels): Use generation to create
> > unique ranges_section_label and ranges_base_label. Return generation.
> > (output_
Hi Richard,
Thanks for reviewing. It's quite lot comment, I am trying to resolve
it one by one. Here I have some questions as embedded.
On Mon, Nov 20, 2017 at 2:46 PM, Richard Biener
wrote:
> On Thu, Nov 16, 2017 at 4:18 PM, Bin.Cheng wrote:
>> On Tue, Oct 24, 2017 at 3:30 PM, Michael Matz w
Hi,
while updating cgraph_node::create_clone I forgot that it also is used to create
inline clones. In that case we can not preserve original local count even if
prof_count is 0.
Bootstrapped/regtested x86_64-linux, comitted.
Honza
* cgraphclones.c (cgraph_node::create_clone): Fix updat
On Thu, Nov 23, 2017 at 04:32:43PM +0100, Martin Jambor wrote:
> > struct A { short s; long i; long j; };
> > struct A a, b;
> > void foo ()
> > {
> > struct A c;
> > __builtin_memcpy (&c, &b, sizeof (struct A));
> > __builtin_memcpy (&a, &c, sizeof (struct A));
> > }
> > int main()
> > {
> >
Hi,
On Mon, Nov 13 2017, Richard Biener wrote:
> The main concern here is that GIMPLE is not very well defined for
> aggregate copies and that gimple-fold.c happily optimizes
> memcpy (&a, &b, sizeof (a)) into a = b;
>
> struct A { short s; long i; long j; };
> struct A a, b;
> void foo ()
> {
>
Michael Matz writes:
> Hi,
>
> On Thu, 23 Nov 2017, Richard Sandiford wrote:
>
>> > I don't want variable-size vector special-casing everywhere. I want
>> > it to be somehow naturally integrating with existing stuff.
>>
>> It's going to be a special case whatever happens though.
>
> It wouldn't
On 11/23/2017 05:49 AM, Richard Biener wrote:
> On Thu, Nov 23, 2017 at 1:16 AM, Jeff Law wrote:
>>
>> Clients of the evrp range analysis may not have initialized the SCEV
>> infrastructure, and in fact my not want to (DOM for example).
>>
>> Yet inside both vr-values.c and gimple-ssa-evrp-analyze
Hi,
The attached patch fixes PR 83111.
Committed to mainline as r255096 and to GCC 7 branch as r255097.
Cheers,
Oleg
gcc/ChangeLog
PR target/83111
* config/sh/sh.md (udivsi3, divsi3, sibcall_value_pcrel,
sibcall_value_pcrel_fdpic): Use local variable instead of
o
On Thu, Nov 23, 2017 at 02:43:32PM +0100, Michael Matz wrote:
> > If it's a VEC_PERM_EXPR then it'll be a new form of VEC_PERM_EXPR.
>
> No, it'd be a VEC_PERM_EXPR where the magic mask is generated by a new
> EXPR type, instead of being a mere constant.
Or an internal function that would produc
On Thu, Nov 23, 2017 at 3:58 PM, Ramana Radhakrishnan
wrote:
> On Thu, Nov 23, 2017 at 1:53 PM, Janne Blomqvist
> wrote:
>> On Thu, Nov 23, 2017 at 2:56 PM, Janne Blomqvist
>> wrote:
>>> On Wed, Nov 22, 2017 at 8:10 PM, Thomas Koenig
>>> wrote:
Hi Janne,
>> So, attached is a new
On Thu, Nov 23, 2017 at 1:53 PM, Janne Blomqvist
wrote:
> On Thu, Nov 23, 2017 at 2:56 PM, Janne Blomqvist
> wrote:
>> On Wed, Nov 22, 2017 at 8:10 PM, Thomas Koenig wrote:
>>> Hi Janne,
>>>
> So, attached is a new version of the patch. No update
> on the ChangeLog. OK for trunk?
>>
On Thu, Nov 23, 2017 at 2:56 PM, Janne Blomqvist
wrote:
> On Wed, Nov 22, 2017 at 8:10 PM, Thomas Koenig wrote:
>> Hi Janne,
>>
So, attached is a new version of the patch. No update
on the ChangeLog. OK for trunk?
>>>
>>> Yup, just really fix the copyright and string length stuff first.
Hi,
On Thu, 23 Nov 2017, Richard Sandiford wrote:
> > I don't want variable-size vector special-casing everywhere. I want
> > it to be somehow naturally integrating with existing stuff.
>
> It's going to be a special case whatever happens though.
It wouldn't have to be this way. It's like sa
On Thu, Nov 23, 2017 at 02:13:57PM +0100, Mark Wielaard wrote:
> Early debug broke generation of .debug_rnglists when using both -gdwarf5
> and -gsplit-dwarf. It introduces a generation for init_sections_and_labels,
> but doesn't account for the generation of up to 4 unique ranges labels,
> two cre
On Thu, 23 Nov 2017, Richard Biener wrote:
On Wed, Nov 22, 2017 at 6:34 PM, Marc Glisse wrote:
Hello,
I hadn't implemented this simplification because I think it is invalid code,
but apparently people do write it, so we might as well handle it sensibly.
This also happens to work around PR 831
Early debug broke generation of .debug_rnglists when using both -gdwarf5
and -gsplit-dwarf. It introduces a generation for init_sections_and_labels,
but doesn't account for the generation of up to 4 unique ranges labels,
two created in init_sections_and_labels and two in output_rnglists.
Fix this b
On Wed, Nov 22, 2017 at 8:10 PM, Thomas Koenig wrote:
> Hi Janne,
>
>>> So, attached is a new version of the patch. No update
>>> on the ChangeLog. OK for trunk?
>>
>> Yup, just really fix the copyright and string length stuff first. Thanks!
>
>
> Committed as rev 255070 with the fixes.
>
> There
On Thu, Nov 23, 2017 at 1:16 AM, Jeff Law wrote:
>
> Clients of the evrp range analysis may not have initialized the SCEV
> infrastructure, and in fact my not want to (DOM for example).
>
> Yet inside both vr-values.c and gimple-ssa-evrp-analyze.c we have calls
> into SCEV (that will fault/abort i
On Wed, Nov 22, 2017 at 6:34 PM, Marc Glisse wrote:
> Hello,
>
> I hadn't implemented this simplification because I think it is invalid code,
> but apparently people do write it, so we might as well handle it sensibly.
> This also happens to work around PR 83104 (already fixed).
>
> bootstrap+regt
On 11/23/2017 12:06 PM, Boris Kolpackov wrote:
> JonY <10wa...@gmail.com> writes:
>
>> Libtool shouldn't matter since it is not used to build those, [...]
>
> We don't know which build system the plugin author will use to build
> the plugin. We can, however, reasonably expect that it will be able
On Thu, Nov 23, 2017 at 10:51 AM, Alan Hayward wrote:
>
>> On 22 Nov 2017, at 16:57, Kilian Verhetsel
>> wrote:
>>
>>
>> Thank you both for your comments.
>>
>> I have added the check to ensure the index vector won't cause an
>> overflow. I also added tests to the testsuite in order to check tha
JonY <10wa...@gmail.com> writes:
> Libtool shouldn't matter since it is not used to build those, [...]
We don't know which build system the plugin author will use to build
the plugin. We can, however, reasonably expect that it will be able
to produce a shared library with the platform-standard ex
On Thu, Nov 23, 2017 at 12:37:31PM +0100, Richard Biener wrote:
> Hum. But that pessimizes a _lot_ of early folding. Like we'd no
> longer optimize
>
> r = &a.a[4];
> r = r + 1;
> if (r != &a.a[0])
>
> and similar stuff exposed a lot by C++ abstraction. We really only
> want to avoid eli
On Thu, 23 Nov 2017, Jakub Jelinek wrote:
> On Thu, Nov 23, 2017 at 11:30:22AM +0100, Richard Biener wrote:
> > FAIL: gcc.c-torture/execute/builtins/memcpy-chk.c execution, -O2
> > ...
> > FAIL: gcc.c-torture/execute/builtins/memmove-chk.c execution, -O2
> > ...
> > FAIL: gcc.c-torture/execute
On 11/22/2017 11:14 AM, Boris Kolpackov wrote:
> JonY <10wa...@gmail.com> writes:
>
>> Is there a problem with using .so for internal libraries instead of
>> "dll"...
>
> I think not but I haven't tested it. The problem with using .so instead
> of .dll is that producing this non-standard extensio
On 22/11/17 14:53, Ramana Radhakrishnan wrote:
> Hi,
>
> I received a private report from a customer that gcc was putting out
> calls to __divdf3 when compiling with +nosimd. When the reciprocal math
> support was added this was probably an oversight or a typo.
>
> The canonical examples is :
>
Richard Biener writes:
> On Tue, Nov 21, 2017 at 11:47 PM, Richard Sandiford
> wrote:
>> Richard Biener writes:
>>> On Mon, Nov 20, 2017 at 1:35 PM, Richard Sandiford
>>> wrote:
Richard Biener writes:
> On Mon, Nov 20, 2017 at 12:56 AM, Jeff Law wrote:
>> On 11/09/2017 06:24 AM,
> On 22 Nov 2017, at 17:33, Jeff Law wrote:
>
> On 11/22/2017 04:31 AM, Alan Hayward wrote:
>>
>>> On 21 Nov 2017, at 03:13, Jeff Law wrote:
>
> You might also look at TARGET_HARD_REGNO_CALL_PART_CLOBBERED. I'd
> totally forgotten about it. And in fact it seems to come pre
On Thu, Nov 23, 2017 at 11:30:22AM +0100, Richard Biener wrote:
> FAIL: gcc.c-torture/execute/builtins/memcpy-chk.c execution, -O2
> ...
> FAIL: gcc.c-torture/execute/builtins/memmove-chk.c execution, -O2
> ...
> FAIL: gcc.c-torture/execute/builtins/strncat-chk.c execution, -O2
> ...
> FAIL:
On Wed, 22 Nov 2017, Richard Biener wrote:
> On Wed, 22 Nov 2017, Jakub Jelinek wrote:
>
> > On Wed, Nov 22, 2017 at 11:41:24AM +0100, Richard Biener wrote:
> > >
> > > I am testing the following (old) patch to value number call lhs
> > > according to the ERF_RETURNS_ARG annotation. This allows
Hi Charles,
On 20/11/17 21:09, Charles Baylis wrote:
On 15 September 2017 at 18:01, Kyrill Tkachov
wrote:
>
> On 15/09/17 16:38, Charles Baylis wrote:
>>
>> On 13 September 2017 at 10:02, Kyrill Tkachov
>> wrote:
>>>
>>> Hi Charles,
>>>
>>> On 12/09/17 09:34, charles.bay...@linaro.org wrote:
> On 22 Nov 2017, at 16:57, Kilian Verhetsel
> wrote:
>
>
> Thank you both for your comments.
>
> I have added the check to ensure the index vector won't cause an
> overflow. I also added tests to the testsuite in order to check that the
> loop is vectorized for UINT_MAX - 1 iterations but no
Sorry, I think in this version of this patch they are fixed.
> -Original Message-
> From: Joseph Myers [mailto:jos...@codesourcery.com]
> Sent: Wednesday, November 22, 2017 6:23 PM
> To: Koval, Julia
> Cc: Jeff Law ; Jakub Jelinek ; GCC
> Patches
> Subject: RE: [patch] remove cilk-plus
>
Hi!
While looking at this function, I found so many formatting issues
(indentation and spacing) that I've decided to post a patch. As an
additional cleanup, I've moved the temp and g declarations to the top of
the function, so that {}s don't need to clutter most of the cases.
The patch shouldn't
Uros,
Thank you for review. New patch with addressed comments is attached.
Could you please merge it?
Thank you
Sergey
2017-11-23 Sergey Shalnov
gcc/
* config/i386/i386.h (TARGET_PREFER_AVX256): Also
enable when TARGET_PREFER_AVX128 is set.
-Original Message-
From: U
This fixes an old missed optimization in alias disambiguation during
SCCVN. We can skip a clobbering stmt if that is a store with exactly
the same value as a preceeding redundancy.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied to trunk.
Richard.
2017-11-23 Richard Biener
On Wed, Nov 22, 2017 at 11:46 AM, Eric Botcazou wrote:
> Hi,
>
> this is a revised version of:
> https://gcc.gnu.org/ml/gcc-patches/2017-11/msg01452.html
>
> with the following changes:
> 1. integration of Bernhard's patch for the Fortran front-end,
> 2. Sandra's fix for the documentation,
>
On Wed, 22 Nov 2017, Jakub Jelinek wrote:
> Hi!
>
> store_expr which is called if to_rtx is a CONCAT and from has complex mode
> covering the whole to_rtx can handle the case when from expands to a CONCAT
> or if it has the same complex mode, but if e.g. one mode is CTImode and
> the other mode i
On Tue, Nov 21, 2017 at 11:47 PM, Richard Sandiford
wrote:
> Richard Biener writes:
>> On Mon, Nov 20, 2017 at 1:35 PM, Richard Sandiford
>> wrote:
>>> Richard Biener writes:
On Mon, Nov 20, 2017 at 12:56 AM, Jeff Law wrote:
> On 11/09/2017 06:24 AM, Richard Sandiford wrote:
>> ..
This is the real fix. The issue is that get_representative_for returns
the first SSA name with the value it finds which can be a non-leader.
But we're shoving this into the expression simplification machinery
which then ends up picking up bogus SSA range info.
Bootstrapped and tested on x86_64-u
On Wed, 22 Nov 2017, Christophe Lyon wrote:
> On 22 November 2017 at 09:44, Richard Biener wrote:
> >
> > The following fixes if-conversion to free SCEV/niter estimates because
> > it DCEs stmts.
> >
> > Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
> >
> > Richard.
> >
> > 2017-1
On Wed, Nov 22, 2017 at 08:25:35AM -0700, Kevin Buettner wrote:
> On Sat, 4 Nov 2017 21:39:14 -0700
> Kevin Buettner wrote:
>
> > On Tue, 31 Oct 2017 08:03:22 +0100
> > Jakub Jelinek wrote:
> >
> > > On Mon, Oct 30, 2017 at 04:06:15PM -0700, Kevin Buettner wrote:
> > > > This patch adds a new
79 matches
Mail list logo
