check for undefined overflow in (T)(P + A) - (T)P - (T)A.
Issue a strict overflow warning if appropriate.
testsuite/ChangeLog:
2014-06-22 Bernd Edlinger bernd.edlin...@hotmail.de
* gcc.c-torture/execute/20140622-1.c: New test.
patch-forwprop.diff
Description: Binary data
On Sat, Jun 21, 2014 at 6:32 PM, Marc Glisse marc.gli...@inria.fr wrote:
Er, I am sorry, I don't know what happened, but when testing the backport to
4.9 I got an obvious failure in the testsuite, which I am sure should also
happen on trunk, but somehow I didn't see it (I am almost sure I
The following is just a prototype to try out a new qualifier type tag
proposed for DWARFv5. There is not even a draft yet of DWARFv5, so this
is just based on a proposal that might or might not be adopted and/or
changed http://dwarfstd.org/ShowIssue.php?issue=131112.1
I have a corresponding patch
Fixes unused mode and in_p argument names. Neither mips_move_to_gpr_cost
nor mips_move_from_gpr_cost care about the mode now, so I just removed it.
Thanks,
Richard
gcc/
* config/mips/mips.c (mips_move_to_gpr_cost): Remove mode argument.
(mips_move_from_gpr_cost): Likewise.
Convert references to gcc.gnu.org to use https.
Shorten textual reference to GCC Bugzilla.
Committed.
Gerald
Index: contribute.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/contribute.html,v
retrieving revision 1.83
diff -u -r1.83
(define_insn rotlmode3
- [(set (match_operand:GPR 0 gpc_reg_operand =r,r)
- (rotate:GPR (match_operand:GPR 1 gpc_reg_operand r,r)
- (match_operand:GPR 2 reg_or_cint_operand r,n)))]
+ [(set (match_operand:GPR 0 gpc_reg_operand =r)
+ (rotate:GPR (match_operand:GPR 1
The new testcases also declare main() as void, but return 0.
- David
On Fri, Jun 20, 2014 at 10:43 PM, Jan Hubicka hubi...@ucw.cz wrote:
Index: testsuite/gcc.dg/localalias.c
===
--- testsuite/gcc.dg/localalias.c (revision
On Sat, Jun 21, 2014 at 10:46 PM, Segher Boessenkool
seg...@kernel.crashing.org wrote:
Nothing will ever generate RTL matching this alternative. Maybe long
ago this was needed, but not anymore.
Can you provide some reference for that assertion?
At some point GCC created shifts with zero shift
Nothing will ever generate RTL matching this alternative. Maybe long
ago this was needed, but not anymore.
Can you provide some reference for that assertion?
At some point GCC created shifts with zero shift count. It probably
does not, but does a generic optimization prevent this?
All
On Sat, Jun 21, 2014 at 10:46 PM, Segher Boessenkool
seg...@kernel.crashing.org wrote:
Nothing will ever generate RTL matching this alternative. Maybe long
ago this was needed, but not anymore.
Bootstrapped and tested on powerpc64-linux, {-m64,-m64/-mtune=power8,
-m32,-m32/-mpowerpc64}, no
On Sat, Jun 21, 2014 at 10:46 PM, Segher Boessenkool
seg...@kernel.crashing.org wrote:
For this create a new mode_attr hH.
Also change i constraints on the shift amount to n, which better
describes what it really is (GCC takes the integer value of these
operands and does arithmetic on them;
On Sat, Jun 21, 2014 at 10:46 PM, Segher Boessenkool
seg...@kernel.crashing.org wrote:
As the previous patch.
Bootstrapped and tested on powerpc64-linux, {-m64,-m64/-mtune=power8,
-m32,-m32/-mpowerpc64}, no regressions. Okay to apply?
Segher
gcc/
* config/rs6000/rs6000.md
On Sat, Jun 21, 2014 at 10:47 PM, Segher Boessenkool
seg...@kernel.crashing.org wrote:
This uses the rotl* extended mnemonics instead of the rlw*nm and rld*cl
mnemonics, because they are shorter and more importantly they look the
same for 32-bit and 64-bit.
Bootstrapped and tested on
On Sat, Jun 21, 2014 at 10:47 PM, Segher Boessenkool
seg...@kernel.crashing.org wrote:
The last (and ugliest) kind of shift.
Bootstrapped and tested on powerpc64-linux, {-m64,-m64/-mtune=power8,
-m32,-m32/-mpowerpc64}, no regressions. Okay to apply?
Segher
2014-06-21 Segher Boessenkool
On Sat, Jun 21, 2014 at 10:47 PM, Segher Boessenkool
seg...@kernel.crashing.org wrote:
All instructions that are var_shift for some alternative have the shift
amount as operands[2].
This patch introduces an attribute maybe_var_shift. If that is set to
yes, the default value of var_shift is
Hello,
a trivial patch to remove a duplicated option, you can see the second one
4 lines below in the patch. (the mixed use of single or double spaces in
this list is strange)
This was included in the bootstrap of another patch.
2014-06-23 Marc Glisse marc.gli...@inria.fr
*
Hello,
I followed the advice in this discussion:
https://gcc.gnu.org/ml/gcc-patches/2014-04/msg00269.html
and here is a new patch. I made an effort to isolate a path in at least
one subcase so it doesn't look too strange that the warning is in this
file. Computing the dominance info just to
On Sat, Jun 21, 2014 at 8:07 PM, Jakub Jelinek ja...@redhat.com wrote:
--- gcc/config/i386/driver-i386.c.jj2014-05-14 14:45:54.0 +0200
+++ gcc/config/i386/driver-i386.c 2014-06-20 18:59:57.805006358 +0200
@@ -745,6 +745,11 @@ const char *host_detect_local_cpu (int a
The new testcases also declare main() as void, but return 0.
I fixed that with previous commit too (what happened is that I managed to
copy wrong version of the files while testing that they fail on AIX.
They indeed did fail, but for wrong versoin)
Honza
On Mon, 2 Jun 2014, Marek Polacek wrote:
* c-typeck.c (parser_build_binary_op): Warn when logical not is used
on the left hand side operand of a comparison.
This...
+/* Warn about logical not used on the left hand side operand of a comparison.
...and this...
+ warning_at
On Mon, 9 Jun 2014, Jonathan Wakely wrote:
This fairly tedious patch refreshes the FAQ, including adding some
notes saying This answer is old and probably no longer relevant to
several answers referring to problems in the GCC 3.x era.
I'm wondering, should those old items be removed? GCC 3.x
Many targets do not have both rotate and rotatert. Of the 47 targets
in the tree, 17 have both, 9 have only rotate, 2 have only rotatert, and
19 have neither (this is based on grep -wil so it can be slightly off).
rs6000 has only rotate, and mips has only rotatert. For such targets
simplifying
On 05/14/2014 12:49 PM, Richard Sandiford wrote:
Jeff Law l...@redhat.com writes:
On 05/13/14 14:11, Sandra Loosemore wrote:
2014-05-13 Catherine Moore c...@codesourcery.com
Sandra Loosemore san...@codesourcery.com
gcc/
* config/mips/mips.c
-Original Message-
From: Jakub Jelinek [mailto:ja...@redhat.com]
Sent: 2014年6月21日 5:24
To: Hale Wang
Cc: 'Mike Stump'; Richard Biener; Mike Stump; GCC Patches
Subject: Re: [Committed] [PATCH] PR61123 : Fix the ABI mis-matching error
caused by LTO
On Fri, Jun 20, 2014 at
On 18 June 2014 05:32, Jeff Law l...@redhat.com wrote:
On 06/11/14 03:35, Zhenqiang Chen wrote:
Thanks for the comments. df_live seams redundant.
With flag_ira_loop_pressure, the pass will call df_analyze () at the
beginning, which can make sure all the DF info are correct.
Can we
On Fri, 13 Jun 2014, Jan Hubicka wrote:
When you extract the address and use it. For example when you
do auto-parallelization and outline a part of your function it
passes arrays as addresses.
Or if you start to introduce address induction variables like
the
Hi,
this is patch to add the used_by_single_function flag to varpool. In full
generality
it is a simple dataflow problem, since the variable may be referred by other
variables
as long as all of them are used by one function only. I have
bootstrapped/regtested it
on x86_64-linux and
Hi Richard,
In this change:
https://gcc.gnu.org/ml/gcc-patches/2014-06/msg01278.html
where substitute_and_fold() was changed to use a dom walker, the calls
to purge dead EH edges during the walk can alter the dom-tree, and have
chaotic results; the testcase in PR 61554 has some blocks traversed
28 matches
Mail list logo
