On Thu, 26 May 2016, Jonathan Wakely wrote:
On 25/05/16 14:54 +0100, Jonathan Wakely wrote:
On 23/05/16 20:39 +0200, Marc Glisse wrote:
Ping
(re-attaching, I just added a one-line comment before the tag class as
asked by Ville)
This is OK for trunk - thanks.
On second thoughts - does
+, etc), and in
others they don't (conversions in general). We have scalarish_type_p for
things that are scalars or vectors, we could add arithmeticish_type_p ;-)
(I think the name arithmetic comes directly from the standard, so we don't
want to change its meaning)
--
Marc Glisse
ps g++ from
doing the expected implicit conversions, but I can't figure out which
rule that is. The fact clang handles the code without an issue does
not help either. Any help will be appreciated.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57572
--
Marc Glisse
Ping
(re-attaching, I just added a one-line comment before the tag class as
asked by Ville)
On Thu, 21 Apr 2016, Marc Glisse wrote:
On Thu, 21 Apr 2016, Jonathan Wakely wrote:
On 20 April 2016 at 21:42, Marc Glisse wrote:
Hello,
does anyone remember why the move constructor
ay require extra :s). It could also interfere with a narrowing/promotion
pass.
Bootstrap+regtest on powerpc64le-unknown-linux-gnu.
2016-05-23 Marc Glisse <marc.gli...@inria.fr>
gcc/
* match.pd (a * (1 << b), ~x & ~y, ~X ^ ~Y, (X ^ Y) ^ Y, ~ (-A),
~ (A - 1), ~(~X >
On Fri, 20 May 2016, Andi Kleen wrote:
On Fri, May 20, 2016 at 05:11:59PM +0200, Marc Glisse wrote:
On Fri, 20 May 2016, Andi Kleen wrote:
Richard Biener <rguent...@suse.de> writes:
The following patch adds BIT_FIELD_INSERT, an operation to
facilitate doing bitfield inserts on reg
helped by BIT_FIELD_INSERT (PDEP seems too hard).
There is one BMI1 instruction we don't use much, bextr (only defined with
an UNSPEC in i386.md, unlike the TBM version), but it is about extracting.
--
Marc Glisse
On Fri, 20 May 2016, Marc Glisse wrote:
Hello,
this was bootstrapped and regtested on powerpc64le-unknown-linux-gnu.
2016-05-20 Marc Glisse <marc.gli...@inria.fr>
PR tree-optimization/71079
PR tree-optimization/71206
gcc/
* match.pd ((X ^ Y) ^ (X ^ Z)): C
Hello,
this was bootstrapped and regtested on powerpc64le-unknown-linux-gnu.
2016-05-20 Marc Glisse <marc.gli...@inria.fr>
gcc/
* match.pd ((X ^ Y) ^ (X ^ Z)): Convert the arguments.
gcc/testsuite/
* gcc.dg/tree-ssa/pr71206.c: New testcase.
--
Marc GlisseIndex: gcc/ma
On Tue, 17 May 2016, Richard Biener wrote:
On Fri, May 13, 2016 at 3:36 PM, Marc Glisse <marc.gli...@inria.fr> wrote:
On Fri, 13 May 2016, Mikhail Maltsev wrote:
I don't know if we might want some :c / single_use restrictions, maybe on
the
outer convert and the rshift/rotate.
I don't
- your call on asserting the variable is not a
pointer before calling set_range_info. Similarly on the check that the
TYPE_PRECISION (TREE_TYPE (tem)) > 1.
--
Marc Glisse
).
Bootstrap+regtest on powerpc64le-unknown-linux-gnu.
2016-05-17 Marc Glisse <marc.gli...@inria.fr>
gcc/
* match.pd (X & C): New transformation.
gcc/testsuite/
* gcc.dg/tree-ssa/and-1.c: New testcase.
--
Marc GlisseIndex: gc
On Mon, 16 May 2016, Jeff Law wrote:
Please use if (GIMPLE
&& ((get_nonzero_bits ...)
Rather than #if GIMPLE
Richard asked for the reverse in some previous patch:
https://gcc.gnu.org/ml/gcc-patches/2016-04/msg01617.html
I don't really care which one we settle on...
--
Marc Glisse
are doing bit_not on it, but it looks
like I should because we can do bitops on pointers?
Adjustment for pr69270.c is exactly the same as in the previous patch from
today :-)
Bootstrap+regtest on powerpc64le-unknown-linux-gnu.
2016-05-16 Marc Glisse <marc.gli...@inria.fr>
-gnu.
2016-05-16 Marc Glisse <marc.gli...@inria.fr>
gcc/
* tree-vrp.c (simplify_truth_ops_using_ranges): Set range
information for new SSA_NAME.
(simplify_switch_using_ranges): Get range through get_range_info
instead of get_value_range.
gcc/tes
will
happen in gimple (most likely the first forwprop pass).
The patch looks good to me, now wait for Richard's comments.
--
Marc Glisse
ts.
Just to be sure: is the fact that VRP doesn't apply fold_stmt on purpose?
The restriction makes sense, it is just that it may yield a bit of
duplication. We already indirectly use get_range_info in match.pd and may
miss out on opportunities that only occur in branches during the VRP pass.
On Wed, 11 May 2016, Jeff Law wrote:
On 05/11/2016 10:17 AM, Marc Glisse wrote:
The transformation seems right to me, but we are then missing another
transformation like ~X & Y -> X ^ Y when we know that X & ~Y is 0 (the 1
bits of X are included in those of Y). That may
On Wed, 11 May 2016, Marc Glisse wrote:
We could also use set_range_info and make simplify_conversion_using_ranges
use get_range_info instead of get_value_range.
Something like this seems to fix the testcase. I'll try to submit it
properly, but I don't know when. (I also added the ~X
move the whole
function to match.pd then ;-)
--
Marc Glisse
iable y, and by the time the next
VRP pass comes, it is too late.
In the mean time, I propose xfailing this test...
--
Marc Glisse
On Tue, 10 May 2016, Mikhail Maltsev wrote:
On 05/08/2016 10:57 PM, Marc Glisse wrote:
On Sun, 8 May 2016, Mikhail Maltsev wrote:
Hi!
I decided to revive this patch:
https://gcc.gnu.org/ml/gcc-patches/2015-06/msg00999.html.
I addressed review comments about sign conversions. Bootstrapped
On Fri, 6 May 2016, Marc Glisse wrote:
Here they are. I did (X) and (X)&(X). The next one would be
((X)), but at some point we have to defer to reassoc.
I didn't add the convert?+tree_nop_conversion_p to the existing transform I
modified. I guess at some point we should make a pass and
y/must be non-zero. It may be
possible to enhance it to handle this case.
--
Marc Glisse
how_bug.cgi?id=28367 (reading an element
from a vector through a union)?
--
Marc Glisse
On Fri, 6 May 2016, Marc Glisse wrote:
2016-05-06 Marc Glisse <marc.gli...@inria.fr>
gcc/
* fold-const.c (fold_binary_loc) [(X ^ Y) & Y]: Remove and merge with...
* match.pd ((X & Y) ^ Y): ... this.
((X & Y) & Y, (X | Y) | Y, (X ^ Y) ^ Y, (X
transformations are safe for any kind of
conversion?
--
Marc Glisse
On Fri, 6 May 2016, Ville Voutilainen wrote:
On 6 May 2016 at 20:51, Marc Glisse <marc.gli...@inria.fr> wrote:
Hi Ville,
since you wrote the latest patches on tuple constructors, do you have an
opinion on this patch, or alternate strategies to achieve the same goal?
https://gcc.gnu.
Hi Ville,
since you wrote the latest patches on tuple constructors, do you have an
opinion on this patch, or alternate strategies to achieve the same goal?
https://gcc.gnu.org/ml/libstdc++/2016-04/msg00041.html
On Thu, 21 Apr 2016, Marc Glisse wrote:
On Thu, 21 Apr 2016, Jonathan Wakely
On Tue, 3 May 2016, Richard Biener wrote:
On Tue, May 3, 2016 at 3:26 PM, Marc Glisse <marc.gli...@inria.fr> wrote:
On Tue, 3 May 2016, Richard Biener wrote:
On Tue, May 3, 2016 at 8:36 AM, Marc Glisse <marc.gli...@inria.fr> wrote:
This removes the duplication. I also remo
in case hat helps.
https://gcc.gnu.org/about.html#cvs
You can send a diff to gcc-patc...@gcc.gnu.org to propose a patch
(possibly Cc: the fortran mailing-list if your patch is related), same as
code changes.
--
Marc Glisse
On Tue, 3 May 2016, Richard Biener wrote:
On Tue, May 3, 2016 at 8:36 AM, Marc Glisse <marc.gli...@inria.fr> wrote:
This removes the duplication. I also removed the case (A)&(A) which is
handled by reassoc. And I need 2 NOP checks, for the case where @0 is a
constant (that could
64le-unknown-linux-gnu.
2016-05-03 Marc Glisse <marc.gli...@inria.fr>
* match.pd ((A | B) & (A | C)): Generalize to BIT_XOR_EXPR. Mark
as commutative. Check both conversions are NOP.
((A & B) OP (C & B)): Remove.
--
Marc Gli
On Mon, 2 May 2016, Richard Biener wrote:
On Sat, Apr 30, 2016 at 8:44 PM, Marc Glisse <marc.gli...@inria.fr> wrote:
Hello,
this case seemed to be missing in the various X cmp X transformations. It
does not change the generated code in the testcase.
The missing :c is rather trivial.
Hello,
this case seemed to be missing in the various X cmp X transformations. It
does not change the generated code in the testcase.
The missing :c is rather trivial. I can commit it separately if you
prefer.
Bootstrap+regtest on powerpc64le-unknown-linux-gnu.
2016-05-02 Marc Glisse
On Fri, 29 Apr 2016, Richard Biener wrote:
Another option is to move the enum declaration from flag-types.h to
coretypes.h. I think I like that best.
This works.
2016-05-02 Marc Glisse <marc.gli...@inria.fr>
gcc/
* flag-types.h (enum warn_strict_overflow_code)
ee-ssa-scopedtables.c. Including options.h in those 2 files seems to
work (I didn't check if all the files in config/ that include
fold-const.h also indirectly include options.h). If you really think
that's better, I'll do it...
--
Marc Glisse
enabled for both.
--
Marc Glisse
Apr 2016, Marc Glisse wrote:
On Tue, 26 Apr 2016, Richard Biener wrote:
On Sun, Apr 24, 2016 at 7:14 PM, Marc Glisse <marc.gli...@inria.fr> wrote:
Hello,
trying to move a first pattern from fold_comparison.
I first tried without single_use. It brought the number of 'free' in
g++.dg/tr
On Tue, 26 Apr 2016, Richard Biener wrote:
On Sun, Apr 24, 2016 at 7:14 PM, Marc Glisse <marc.gli...@inria.fr> wrote:
Hello,
trying to move a first pattern from fold_comparison.
I first tried without single_use. It brought the number of 'free' in
g++.dg/tree-ssa/pr61034.C down to 11, c
interoperability, even for in-tree builds.
It is just a matter what versions we want to test, I have not really
any idea where the limits will be, just that it can no longer be 4.3.2.
Even if in-tree builds work with several versions, we may still want to
document only one as supported.
--
Marc Glisse
gmp-6.1.1 is supposed to be out any day now and will not require
-DNO_ASM anymore.
--
Marc Glisse
On Tue, 26 Apr 2016, Richard Biener wrote:
On Sun, Apr 24, 2016 at 7:42 PM, Marc Glisse <marc.gli...@inria.fr> wrote:
Hello,
the first part is something that was discussed last stage3, and Jakub argued
in favor of single_use. The second part is probably less useful, it notices
that
uted_op(op) at the
place where the regular commutation gets lowered. If it is significantly
more complicated, I guess it isn't that urgent...
--
Marc Glisse
ind?
--
Marc Glisse
ator new wrote there. Depending on inline decisions, DSE-ing part of
new could be problematic (IIRC those functions are technically not allowed
to be marked 'inline', but that's not quite the same thing).
--
Marc Glisse
that).
Bootstrap+regtest on powerpc64le-unknown-linux-gnu.
2016-04-26 Marc Glisse <marc.gli...@inria.fr>
gcc/
* genmatch.c (write_predicate): Add ATTRIBUTE_UNUSED.
* fold-const.c (fold_binary_loc): Remove 2 transformations
superseded by match.pd.
* match.pd (x+x
the
result of that function.
Bootstrap+regtest on powerpc64le-unknown-linux-gnu. (hmm, I probably
should have done it on x86_64 instead, I don't know if the ppc backend has
implemented the overflow functions recently)
2016-04-25 Marc Glisse <marc.gli...@inria.fr>
gcc/
* match.pd
On Fri, 22 Apr 2016, Marc Glisse wrote:
On Fri, 22 Apr 2016, Richard Biener wrote:
On Fri, Apr 22, 2016 at 5:29 AM, Marc Glisse <marc.gli...@inria.fr> wrote:
Hello,
this optimizes a common pattern for unsigned overflow detection, when one
of
the arguments turns out to be a co
integers anyway.
I split the equality case, because it was already getting ugly.
Bootstrap+regtest on powerpc64le-unknown-linux-gnu.
2016-04-25 Marc Glisse <marc.gli...@inria.fr>
gcc/
* fold-const.h: Include flag-types.h.
(fold_overflow_warning): Declare.
On Fri, 22 Apr 2016, Kyrill Tkachov wrote:
On 22/04/16 10:43, Kyrill Tkachov wrote:
On 22/04/16 10:42, Marc Glisse wrote:
On Fri, 22 Apr 2016, Kyrill Tkachov wrote:
2016-04-21 Marc Glisse <marc.gli...@inria.fr>
gcc/
* match.pd (min(-x, -y), max(-x, -y), min(~x, ~y), max(
On Fri, 22 Apr 2016, Kyrill Tkachov wrote:
2016-04-21 Marc Glisse <marc.gli...@inria.fr>
gcc/
* match.pd (min(-x, -y), max(-x, -y), min(~x, ~y), max(~x, ~y)):
New transformations.
gcc/testsuite/
* gcc.dg/tree-ssa/minmax-2.c: New testcase.
I see the new testcase f
On Fri, 22 Apr 2016, Richard Biener wrote:
On Fri, Apr 22, 2016 at 5:29 AM, Marc Glisse <marc.gli...@inria.fr> wrote:
Hello,
this optimizes a common pattern for unsigned overflow detection, when one of
the arguments turns out to be a constant. There are more ways this could
look like, (
016-04-22 Marc Glisse <marc.gli...@inria.fr>
gcc/
* match.pd (X + CST CMP X): New transformation.
gcc/testsuite/
* gcc.dg/tree-ssa/overflow-1.c: New testcase.
--
Marc GlisseIndex: gcc/match.pd
===
--- gcc
On Thu, 21 Apr 2016, Jonathan Wakely wrote:
On 20 April 2016 at 21:42, Marc Glisse wrote:
Hello,
does anyone remember why the move constructor of _Tuple_impl is not
defaulted? The attached patch does not cause any test to fail (whitespace
kept to avoid line number changes). Maybe something
need.
We could generalize to cases where overflow is not undefined if we know
(VRP) that the variables are not TYPE_MIN_VALUE, but that didn't look like
a priority.
Bootstrap+regtest on powerpc64le-unknown-linux-gnu.
2016-04-21 Marc Glisse <marc.gli...@inria.fr>
gcc/
* matc
on powerpc64le-unknown-linux-gnu (some noise in libgomp
testcases).
2016-04-21 Marc Glisse <marc.gli...@inria.fr>
gcc/
* match.pd (min(int_max, x), max(int_min, x)): New transformations.
gcc/testsuite/
* gcc.dg/tree-ssa/minmax-1.c: New testcase.
--
Marc GlisseIndex: gcc/ma
for _aligned_free.
I am concerned about what happens when a user replaces a global operator
delete. Does the replacement function have to satisfy the properties for
this attribute?
--
Marc Glisse
be boolean for instance. Asking for
tree_nop_conversion_p between @0 and that type seems strange. Also, you
are not allowed to use TYPE_PRECISION on a vector type.
--
Marc Glisse
iewer), though you could now move the test
tree_expr_nonzero_p next to tree_expr_nonnegative_p (it is redundant for
the last case).
--
Marc Glisse
e it even reaches this pattern. Multiplying by a third
variable 'c' (where the compiler has no idea what the sign of c is)
could be nicer.
Then you'll need to wait for a real reviewer to show up.
--
Marc Glisse
he other transformation has similar issues.
--
Marc Glisse
nt, so that's still invalid. It is also invalid for
unsigned. The :s are useless since the output is a single insn.
--
Marc Glisse
-31 Naveen H.S <naveen.hurugalaw...@caviumnetworks.com>
* match.pd (cmp (mult:cs @0 @1) (mult:cs @2 @1)) : New Pattern.
* gcc.dg/pr31096.c: New testcase.
Looks like you are turning x*-1 < y*-1 into x<y? That doesn't work...
--
Marc Glisse
com>
* fold-const.c (tree_binary_nonnegative_warnv_p) : Handle the case
a * a; where it should be positive always.
* gcc.dg/pr23471.c: New testcase.
Er, the code just below your patch should already handle this case, no?
--
Marc Glisse
On Mon, 28 Mar 2016, Allan Sandfeld Jensen wrote:
On Sunday 27 March 2016, Marc Glisse wrote:
On Sun, 27 Mar 2016, Allan Sandfeld Jensen wrote:
Would it be possible to add constexpr to the intrinsics headers?
For instance _mm_set_XX and _mm_setzero intrinsics.
Already suggested here:
https
On Sun, 27 Mar 2016, Allan Sandfeld Jensen wrote:
Would it be possible to add constexpr to the intrinsics headers?
For instance _mm_set_XX and _mm_setzero intrinsics.
Already suggested here:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65197
A patch would be welcome (I started doing it at
?
--
Marc Glisse
f;
+ v ^= ~v;
+ v &= ~u;
+ v -= -u;
+ return v;
+ }
--
Marc Glisse
On Tue, 22 Mar 2016, Richard Biener wrote:
On March 22, 2016 4:55:13 PM GMT+01:00, Marc Glisse <marc.gli...@inria.fr>
wrote:
On Tue, 22 Mar 2016, Richard Biener wrote:
This adjusts the PR70251 fix as discussed in the PR audit trail
and fixes a bug in genmatch required (bah, stupid G
@2)
It seems that the references to @0 in the "if" should use @1 instead (at
least the last one). I assume this test is to make sure that A has as many
integer elements of the same size as the result of the vec_cond_expr.
Sorry for giving you an incomplete change in the PR.
--
Marc Glisse
On Sun, 20 Mar 2016, Andreas Schwab wrote:
Marc Glisse <marc.gli...@inria.fr> writes:
For most packages, providing CFLAGS for configure is enough, you don't
have to give them *again* to make.
The toplevel GCC Makefile needs to pass down any CFLAGS setting that has
been passed in by th
On Sun, 20 Mar 2016, Bernd Edlinger wrote:
On 20.03.2016 11:03, Marc Glisse wrote:
On Sun, 20 Mar 2016, Bernd Edlinger wrote:
So I looked for a way to disable the asm code, and found it can be
done, but differently than for in-tree gmp. See the attached patch.
As noted in PR 67728
e-assembly,
gcc will still manage to break things because it calls make CFLAGS=-g,
which bypasses the GMP mechanism for defining NO_ASM. We might change that
mechanism at some point in the future in GMP:
https://gmplib.org/list-archives/gmp-devel/2016-March/004257.html
but that's not for right now
patch.
As noted in PR 67728, it seems that gcc's intrusive way of overriding
CFLAGS also breaks GMP itself, not just MPFR, by hiding the macro NO_ASM
that GMP tries to define through its own CFLAGS. So maybe Bernd's patch
should be duplicated to also apply to GMP?
--
Marc Glisse
.c
@@ -0,0 +1,11 @@
+/* PR middle-end/70025 */
+/* { dg-do compile } */
+/* { dg-options "-Wno-psabi" } */
+
+typedef int v8si __attribute__ ((vector_size (32)));
+
+v8si
+foo (v8si v)
+{
+ return v %= -v;
+}
--
Marc Glisse
that route if possible.
Still, if there are some easy cases that can be handled early in match.pd,
that can't hurt... (if there aren't, that's fine)
Just like x+y+x -> 2*x+y is for reassoc, but x+x -> 2*x can be done in
match.pd.
--
Marc Glisse
ave a clear definition for what kinds of member functions
are allowed in an empty type.
--
Marc Glisse
(bit_and:c (test1 @0 @1) (test2 @0 @1))
+ (if (INTEGRAL_TYPE_P (TREE_TYPE (@0))
+|| VECTOR_INTEGER_TYPE_P (TREE_TYPE (@0)))
+{ constant_boolean_node (false, type); })))
+
/* -A CMP -B -> B CMP A. */
(for cmp (tcc_comparison)
scmp (swapped_tcc_comparison)
--
Marc Glisse
amp;& !DECL_ARTIFICIAL (field)
&& !is_empty_record (TREE_TYPE (field)))
return false;
return true;
}
--
Marc Glisse
On Wed, 27 Jan 2016, Jakub Jelinek wrote:
On Wed, Jan 27, 2016 at 09:10:14AM +0100, Marc Glisse wrote:
Revised:
/* Returns true if TYPE is POD of one-byte or less in size for the purpose
of layout and an empty class or an class with empty classes. */
static bool
is_empty_record (tree type
e_type { struct dummy i; };
extern true_type y;
extern void xxx (true_type c);
void
yyy (void)
{
xxx (y);
}
[hjl@gnu-skl-1 gcc]$
--
Marc Glisse
On Tue, 26 Jan 2016, H.J. Lu wrote:
On Tue, Jan 26, 2016 at 12:23 PM, Marc Glisse <marc.gli...@inria.fr> wrote:
On Tue, 26 Jan 2016, H.J. Lu wrote:
On Tue, Jan 26, 2016 at 11:27 AM, Jason Merrill <ja...@redhat.com> wrote:
On 12/14/2015 05:08 PM, H
such
extensions.
--
Marc Glisse
sses than we would
expect.
--
Marc Glisse
On Thu, 14 Jan 2016, Jonathan Wakely wrote:
On 14/01/16 20:13 +0100, Marc Glisse wrote:
I didn't think about it much, but I am worried that __random_not_eq will
accidentally become an associated namespace for more classes than we would
expect.
Yes, it would be an associated namespace
On Tue, 5 Jan 2016, Marc Glisse wrote:
On Tue, 5 Jan 2016, Bernd Edlinger wrote:
an in-tree mpfr build enables inline asm code, which makes the
mips-bootstrap fail,
because at least mpfr 2.4.2 uses the "=h" constraint but in
config/mips/constraints.md
we find: "Former
gmp with
--disable-assembly, the flag -DNO_ASM ends up in __GMP_CFLAGS (in gmp.h)
and mpfr thus uses it automatically.
--
Marc Glisse
for how
to request this, so spamming this list.
my account on gcc.gnu.org/bugzilla is "vap...@gentoo.org".
Permissions are automatic for @gcc addresses, you should create a new
account with that one (you can make it follow the old account, etc).
--
Marc Glisse
LWG issues on the topic,
one saying that the C++11 change didn't go far enough to match reality,
since it still documents C headers differently from the C standard, and
one saying that all overloads of abs should be declared as soon as one is
(yes, they contradict each other).
--
Marc Glisse
, and there are bugs (or standard issues)
about having them in the global namespace for the first one).
--
Marc Glisse
-std.org/jtc1/sc22/wg21/docs/lwg-active.html#2294
--
Marc Glisse
key < .ssh/id_dsa.pub
/home/toon/.ssh/config line 3: Bad protocol spec '1'.
toon@moene:~$ cat .ssh/config
Host gcc.gnu.org
ForwardX11 no
Protocol 1
Any hints ?
Wild guess (that you are using debian testing or unstable):
apt-get install openssh-client-ssh1
ssh1 t...@gcc.gnu.org ...
--
Marc Glisse
t some big
road-block, which there might be), and a little bit more code duplication
as in your patch seems appropriate at this stage.
--
Marc Glisse
be willing to do it on linux-x86, but not on ios/mac
where they dominate and compatibility with their own earlier versions
matters more than compatibility with gcc?
--
Marc Glisse
ressof.
^^
Typo.
/testsuite
* 18_support/nested_exception/68139.cc: New.
--
Marc Glisse
On Fri, 11 Dec 2015, Ville Voutilainen wrote:
On 11 December 2015 at 08:55, Marc Glisse <marc.gli...@inria.fr> wrote:
On Fri, 11 Dec 2015, Ville Voutilainen wrote:
Tested on Linux-PPC64.
2015-12-11 Ville Voutilainen <ville.voutilai...@gmail.com>
PR libstdc++/68139
/
g patterns (described in
fold-const.c and match.pd), like p + n < p in this case.
--
Marc Glisse
in gcc-5, can't you?
--
Marc Glisse
On Wed, 25 Nov 2015, Marc Glisse wrote:
So, I'd really prefer doing x-y>x to y>x only for single use.
Ok
Let me post this patch (needs testing on x86, I only tested on ppc which
does not implement the new optabs) so I can more easily find it again at
next stage 1.
It produces ima
601 - 700 of 1798 matches
Mail list logo
