On 21 October 2014 12:01, Hale Wang wrote:
> Hi,
>
> Some configurations of the Cortex-M0 and Cortex-M1 come with a high latency
> multiplier. This patch adds support for such configurations.
>
> Small multiplier means using add/sub/shift instructions to replace the mul
> instruction for the MCU t
Hi All,
Here is the last part of patch which is related to vectorization
improvements, namely
1. New sub-phase is added which delete dead predicate computations
(such code can prevent loop vectorization since dead computation are
not part of bool pattern tree). It is invoked only under
FLAG_FORC
Code size for spec2000 is almost unchanged (many benchmarks have the
same binaries).
For those that are changed we have the following numbers (200 vs 100,
both dynamic build -Ofast -funroll-loops -flto):
183.equake +10%
164.gzip, 173.applu +3,5%
187.facerec, 191.fma3d +2,5%
200.sixstrack +2%
177.me
Hi!
On Tue, Oct 28, 2014 at 01:44:50PM +0100, Jakub Jelinek wrote:
> On Mon, Oct 27, 2014 at 05:16:05PM +0100, Jakub Jelinek wrote:
> > Here is an updated patch, ok if bootstrap/testing passes (so far just
> > checked with
> > make -j16 -k check RUNTESTFLAGS='--target_board=unix\{-m32,-m64\} asan.
On Tue, Nov 11, 2014 at 04:51:38PM +, Jiong Wang wrote:
> currently, only sanitizer tess (asan/tsan/ubsan) and a couple of fortran test
> will invoke dg-output.
>
> pass x86-64 c/c++ regression.
> pass aarch64-none-linux-gnu c/c++ regression.
This patch broke a few tests in ubsan.exp. The r
Hello Richard,
On 12 Nov 10:23, Richard Biener wrote:
> On Wed, 5 Nov 2014, Ilya Verbin wrote:
> Yes please.
>
> Please make sure that regular LTO bootstrap still works - LTO is
> only tested lightly in the testsuite.
Current main trunk fails to bootstrap w/ `bootstrap-lto':
git/gcc/configure --e
On Wed, 2014-11-12 at 14:16 +0100, Tom de Vries wrote:
I can't speak to the rest of the patch, but one readability nitpick:
> diff --git a/gcc/passes.def b/gcc/passes.def
> index 2305d67..dd91718 100644
> --- a/gcc/passes.def
> +++ b/gcc/passes.def
> @@ -241,6 +241,9 @@ along with GCC; see the fi
On Wed, 12 Nov 2014, Kirill Yukhin wrote:
> Hello Richard,
> On 12 Nov 10:23, Richard Biener wrote:
> > On Wed, 5 Nov 2014, Ilya Verbin wrote:
> > Yes please.
> >
> > Please make sure that regular LTO bootstrap still works - LTO is
> > only tested lightly in the testsuite.
>
> Current main trunk
On Wed, 12 Nov 2014, Tom de Vries wrote:
> [ moved from gcc@ to gcc-patches@ ]
> [ subject was: Re: [gomp4] openacc kernels directive support ]
> On 30-09-14 15:37, Tom de Vries wrote:
> > > I would be happily accepting splitting the current autopar pass
> > > that way, that is, do
> > >
> > > NE
Manuel López-Ibáñez writes:
> Index: libcpp/line-map.c
> ===
> --- libcpp/line-map.c (revision 217191)
> +++ libcpp/line-map.c (working copy)
> @@ -631,10 +631,54 @@ linemap_position_for_line_and_column (co
> + ((line - ORDIN
On Wed, Nov 12, 2014 at 10:49:38AM +0100, Richard Biener wrote:
> TYPE_OVERFLOW_WRAPS returns nonsense for !integral types and thus
> this check likely restricts the transform to non-floats for example.
> The macro documentation states "given an integral type ..." thus
> it should be sth like
>
>
On Wed, 12 Nov 2014, Marek Polacek wrote:
> On Wed, Nov 12, 2014 at 10:49:38AM +0100, Richard Biener wrote:
> > TYPE_OVERFLOW_WRAPS returns nonsense for !integral types and thus
> > this check likely restricts the transform to non-floats for example.
> > The macro documentation states "given an in
On Wed, Nov 12, 2014 at 2:13 PM, Jakub Jelinek wrote:
> Hi!
>
> This patch mentions __builtin_*_overflow in gcc-5/changes.html.
> Ok for CVS?
Ok.
Thanks,
Richard.
> --- gcc-5/changes.html 27 Oct 2014 18:05:26 - 1.20
> +++ gcc-5/changes.html 12 Nov 2014 13:09:01 -
> @@ -84,7 +84,3
On 12 November 2014 15:24, Andreas Schwab wrote:
> Manuel López-Ibáñez writes:
>
>> Index: libcpp/line-map.c
>> ===
>> --- libcpp/line-map.c (revision 217191)
>> +++ libcpp/line-map.c (working copy)
>> @@ -631,10 +631,54 @@ linemap_p
On Wed, Nov 12, 2014 at 2:12 PM, Jakub Jelinek wrote:
> On Wed, Nov 12, 2014 at 01:55:12PM +0100, Basile Starynkevitch wrote:
>> Hello All,
>>
>> Some plugins (including MELT, see http://gcc-melt.org/ for more)
>> are made of several C++ source files which all include "plugin-version.h"
>> because
On 12 Nov 15:09, Richard Biener wrote:
> On Wed, 12 Nov 2014, Kirill Yukhin wrote:
>
> > Hello Richard,
> > On 12 Nov 10:23, Richard Biener wrote:
> > > On Wed, 5 Nov 2014, Ilya Verbin wrote:
> > > Yes please.
> > >
> > > Please make sure that regular LTO bootstrap still works - LTO is
> > > only
On 12/11/14 14:09, Marek Polacek wrote:
... prune_gcc_output prunes more than just absolute file paths, it
prunes even the "note: " messages. And several ubsan tests have
/* { dg-output "\[^\n\r]*note: pointer points here\[^\n\r]*(\n|\r\n|\r)" } */
but since the note's are already gone, the te
See libcpp/include/line-map.h:589.
Andreas.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
On Wed, Nov 12, 2014 at 03:35:06PM +0100, Manuel López-Ibáñez wrote:
> > ../../libcpp/line-map.c:667:65: error: suggest braces around empty body in
> > an 'if' statement [-Werror=empty-body]
>
> I just (r217418) bootstrapped this code and it did not produce this
> error (or warning). Could you g
On Wed, Nov 12, 2014 at 3:35 PM, Richard Biener
wrote:
> On Wed, Nov 12, 2014 at 2:12 PM, Jakub Jelinek wrote:
>> On Wed, Nov 12, 2014 at 01:55:12PM +0100, Basile Starynkevitch wrote:
>>> Hello All,
>>>
>>> Some plugins (including MELT, see http://gcc-melt.org/ for more)
>>> are made of several C
> On 12 Nov 2014, at 14:13, Jakub Jelinek wrote:
> + size_t sz;
> + if (__builtin_mul_overflow (x, y, &sz)
Missing right parenthesis ?
On Wed, 12 Nov 2014, Kirill Yukhin wrote:
> On 12 Nov 15:09, Richard Biener wrote:
> > On Wed, 12 Nov 2014, Kirill Yukhin wrote:
> >
> > > Hello Richard,
> > > On 12 Nov 10:23, Richard Biener wrote:
> > > > On Wed, 5 Nov 2014, Ilya Verbin wrote:
> > > > Yes please.
> > > >
> > > > Please make su
On Wed, Nov 12, 2014 at 03:39:25PM +0100, Tristan Gingold wrote:
>
> > On 12 Nov 2014, at 14:13, Jakub Jelinek wrote:
> > + size_t sz;
> > + if (__builtin_mul_overflow (x, y, &sz)
>
> Missing right parenthesis ?
Thanks, fixed.
Jakub
On Mon, 2014-10-13 at 10:33 +0200, Mark Wielaard wrote:
> On Wed, 2014-10-08 at 12:13 +0200, Mark Wielaard wrote:
> > This patch was written a long time ago by Jakub and has been in Fedora
> > gcc for some time. All I did was rebase it to current gcc trunk
> > and add a testcase. Back when it was o
We have been using the wrong register to hold GOT in 64-bit large model,
which is used by the large model PLT. The only reason we haven't run into
any problem is linker doesn't support the large model PLT. I am looking
into linker issue. This patch corrects REAL_PIC_OFFSET_TABLE_REGNUM for
64-bit
On Wed, Nov 12, 2014 at 03:50:19PM +0100, Mark Wielaard wrote:
> On Mon, 2014-10-13 at 10:33 +0200, Mark Wielaard wrote:
> > On Wed, 2014-10-08 at 12:13 +0200, Mark Wielaard wrote:
> > > This patch was written a long time ago by Jakub and has been in Fedora
> > > gcc for some time. All I did was re
On 12 November 2014 15:38, Marek Polacek wrote:
> On Wed, Nov 12, 2014 at 03:35:06PM +0100, Manuel López-Ibáñez wrote:
>> > ../../libcpp/line-map.c:667:65: error: suggest braces around empty body in
>> > an 'if' statement [-Werror=empty-body]
>>
>> I just (r217418) bootstrapped this code and it d
I did suggest this change, so I feel I should defend it!
Our testing of many algorithms is woefully slim, that is how (for
example) the segfaulting bug in std::nth_element got through into a
release -- the tests for that algorithm were terrible, and basically
didn't test the functionality on enoug
On 12 November 2014 15:54, Manuel López-Ibáñez wrote:
> On 12 November 2014 15:38, Marek Polacek wrote:
>> On Wed, Nov 12, 2014 at 03:35:06PM +0100, Manuel López-Ibáñez wrote:
>>> > ../../libcpp/line-map.c:667:65: error: suggest braces around empty body
>>> > in an 'if' statement [-Werror=empty-
On Wed, Nov 12, 2014 at 03:22:41PM +0100, Richard Biener wrote:
> TYPE_OVERFLOW_SANITIZES?
Can I call it sanitize_fold_p and put it as a static inline fn
into tree.h?
Marek
OK.
Jason
On Wed, Nov 12, 2014 at 04:07:33PM +0100, Marek Polacek wrote:
> On Wed, Nov 12, 2014 at 03:22:41PM +0100, Richard Biener wrote:
> > TYPE_OVERFLOW_SANITIZES?
>
> Can I call it sanitize_fold_p and put it as a static inline fn
> into tree.h?
It is a predicate on type, so perhaps sanitized_type_p ?
On Wed, 12 Nov 2014, Jakub Jelinek wrote:
> On Wed, Nov 12, 2014 at 04:07:33PM +0100, Marek Polacek wrote:
> > On Wed, Nov 12, 2014 at 03:22:41PM +0100, Richard Biener wrote:
> > > TYPE_OVERFLOW_SANITIZES?
> >
> > Can I call it sanitize_fold_p and put it as a static inline fn
> > into tree.h?
>
Sorry I forgot about this for so long. The patch is OK.
Jason
On 11 November 2014 15:25, Alan Lawrence wrote:
> [Resending in gcc-patches-accepted form]
>
> I'm working on a patch for vget_lane (that removes the be_checked_get_lane
> thing which isn't an intrinsic). Other than that, no not yet - loads and
> stores I was thinking to wait until David Sherwood
On Wed, Nov 12, 2014 at 3:54 PM, Jakub Jelinek wrote:
> On Wed, Nov 12, 2014 at 03:50:19PM +0100, Mark Wielaard wrote:
>> On Mon, 2014-10-13 at 10:33 +0200, Mark Wielaard wrote:
>> > On Wed, 2014-10-08 at 12:13 +0200, Mark Wielaard wrote:
>> > > This patch was written a long time ago by Jakub and
>> + // The constraint info maintains information about constraints
>> + // associated with the declaration.
>> + tree constraint_info;
>
>
> We talked back at the end of June about moving this into a separate
> hashtable; I'm still reluctant to add another pointer to most declarations
> when on
On Wed, Nov 12, 2014 at 04:21:09PM +0100, Richard Biener wrote:
> On Wed, Nov 12, 2014 at 3:54 PM, Jakub Jelinek wrote:
> > On Wed, Nov 12, 2014 at 03:50:19PM +0100, Mark Wielaard wrote:
> >> On Mon, 2014-10-13 at 10:33 +0200, Mark Wielaard wrote:
> >> > On Wed, 2014-10-08 at 12:13 +0200, Mark Wie
Nice! One nit - can the extra "tree" argument be a "const_tree" ? - I'll defer
to the maintainers on the use of C++ default arguments in the AArch64 backend.
But LGTM.
--Alan
Charles Baylis wrote:
On 11 November 2014 15:25, Alan Lawrence wrote:
[Resending in gcc-patches-accepted form]
I'm
On Wed, 2014-11-12 at 16:33 +0100, Jakub Jelinek wrote:
> On Wed, Nov 12, 2014 at 04:21:09PM +0100, Richard Biener wrote:
> > On Wed, Nov 12, 2014 at 3:54 PM, Jakub Jelinek wrote:
> > > I think we want this (also extended for C11/C++11/C++14 afterwards), even
> > > when the early debug bits won't
Hi!
I have a patch which disables -faggressive-loop-optimizations and
-fstrict-overflow when -fsanitize=undefined is switched on. Compiler
with aggressive optimizations may decrease quality of sanitization by
optimistically proposing something it actually should check.
Details are in https:/
On Wed, Nov 12, 2014 at 2:54 AM, Jiong Wang wrote:
> On 12/11/14 10:01, Yangfei (Felix) wrote:
>
>> + if (GET_MODE (operands[0]) != DImode)
>> + FAIL;
>
>
> shouldn't SImode be considered for -mabi=ilp32 ?
I don't think it is needed for -mabi=ilp32 since word_mode is still
DImode for -
Hi Casar!
Can you please help me trying to understand the following change, that
you've done a long time ago:
On Tue, 8 Jul 2014 07:28:24 -0700, Cesar Philippidis
wrote:
> On 07/07/2014 02:55 AM, Thomas Schwinge wrote:
>
> > On Sun, 6 Jul 2014 16:10:56 -0700, Cesar Philippidis
> > wrote:
> >
Hi,
if I understand correctly the existing uses of tf_ignore_bad_quals, in
order to correctly implement the resolution of CWG 1510, thus accept the
testcases, we have to handle decltypes like references and template type
arguments, thus make sure cp_build_qualified_type_real is called with |
On 11/12/2014 11:01 AM, Yangfei (Felix) wrote:
> +(define_expand "doloop_end"
>> + [(use (match_operand 0 "" "")) ; loop pseudo
>> + (use (match_operand 1 "" ""))] ; label
>> + ""
>> + "
>> +{
Drop the "" surrounding the { }.
r~
On 11 Nov 20:25, Joseph Myers wrote:
> On Tue, 11 Nov 2014, Andi Kleen wrote:
>
> > Joseph Myers writes:
> >
> > > On Tue, 11 Nov 2014, Ilya Enkovich wrote:
> > >
> > >> Hi,
> > >>
> > >> This patch integrates MPX runtime library into GCC source tree. MPX
> > >> runtime is responsible for ini
On Wed, Nov 5, 2014 at 6:50 AM, Kirill Yukhin wrote:
> Hello,
> On 24 Oct 17:56, Yury Gribov wrote:
> ...
>> +const struct test_data_t test_data[] = {
>> + { STRTOL, "-0x8000", 0, -0x8000L, 0 },
> ...
>> + switch (test_data[i].fun)
>> + {
>> + case STRTOL:
>> + r
Ping for the question below.
On 30.10.2014 15:29, Patrick Wollgast wrote:
> Since I haven't heard back for quite a while, I wanted to ask what the
> current stat of the patch is.
>
> Is the patch from the last mail approved (
> https://gcc.gnu.org/ml/gcc-patches/2014-10/msg01524.html ), or should
Hi all,
This patch implements fusion of adrp and add instructions that appear in
RTL as consecutive HIGH and LO_SUM SETs.
This fusion is enabled by default for Cortex-A57 and Cortex-A53.
This depends on the previous macro fusion patch posted at
https://gcc.gnu.org/ml/gcc-patches/2014-11/msg009
Hi all,
I noticed that the check for modified_in_p in sched-deps is not needed
and needlessly restricts the insn pairs that we can check for macro
fusion in the backend hooks.
This patch removes the check. Currently that execution path is only used
in arm and aarch64.
This enables the backen
In several occasions (see [1][2] people requested a switch to tell GCC that a
given compilation unit should not contain any float and that GCC should warn
about any violation of this assumption. Such a switch would ensure that no
softfloat library is going to be pulled in by the linker and would
Hi all,
This patch adds the Cortex-A53 erratum workaround options item to the
changes page
(and adds the AArch64 section of that page in the process)
Ok?
Thanks,
KyrillIndex: htdocs/gcc-5/changes.html
===
RCS file: /cvs/gcc/wwwdoc
On Wed, Nov 12, 2014 at 04:46:39PM +0100, Mark Wielaard wrote:
> I don't mind changing the language hook to return the actual DW_LANG_*
> constant directly, that seems like a nice cleanup.
>
> But I don't think we can just replace TRANSLATION_UNIT_LANGUAGE and
> lang_hooks.name. The name is (expli
Hi Ed,
On 2 Nov 2014, at 01:48, Ed Smith-Rowland wrote:
>
>
please take a look at PR63834, as
https://gcc.gnu.org/ml/gcc-cvs/2014-11/msg00307.html
breaks bootstrap on x86064-darwin12,
the reproducer also segvs on x86-64-linux.
(It looks like the commit was related to this series of patches)
Hi all,
This is a much-delayed respin of the patch in response to Richards
feedback at:
http://gcc.gnu.org/ml/gcc-patches/2014-05/msg00068.html
We now let recursion do its magic and just add the cost of the
arithmetic operation on top.
Tested on arm-none-eabi
Ok for trunk?
2014-11-12 Kyr
Hi,
This patch adds bind_pic_locally to a certain tests that depend on the
availability of functions, declared in them. Those tests fail on
Android (or on any other pic target);
As for gcc/testsuite/g++.dg/fstack-protector-strong.[cC] - this is a
related problem. I've added target nonpic, cause __
On 07/11/14 13:36, Richard Henderson wrote:
On 11/07/2014 01:02 PM, Ramana Radhakrishnan wrote:
+ *cost = COSTS_N_INSNS (aarch64_internal_mov_immediate
+(gen_rtx_REG (mode, 0), x, false));
}
Can't you pass NULL for the register when generate is
Hi,
One of the problems we appear to face with multilib testing especially
with conflicting ABIs in the ARM world is the occasional case where a
testglue file is built for one ABI but gets linked against a multilib
test invocation with another target.
We've tried to ameliorate this in some
Hans Boehm pointed out that we were using dmb sy instead of dmb ish.
Given that the ARM-ARM says that the inner shareability domain is really
the one that contains all PE's controlled by a single hypervisor or
operating system, it would be safe to replace all dmb sy's with dmb ish's.
This is a
014-11-12 17:22 GMT+01:00 Patrick Wollgast :
> Ping for the question below.
>
> On 30.10.2014 15:29, Patrick Wollgast wrote:
>> Since I haven't heard back for quite a while, I wanted to ask what the
>> current stat of the patch is.
>>
>> Is the patch from the last mail approved (
>> https://gcc.gnu
Hi Matthew,
> -Original Message-
> From: Matthew Fortune [mailto:matthew.fort...@imgtec.com]
> Sent: Thursday, November 06, 2014 12:11 PM
> To: Moore, Catherine; 'gcc-patches@gcc.gnu.org' (gcc-
> patc...@gcc.gnu.org); Eric Christopher (echri...@gmail.com)
> Cc: Richard Sandiford; Rich Fuhl
Hi,
I was taking a look at fixing the issues in the ARM back-end exposed
by Marc Glisse's patch in [1], and hoped to fix them by adapting the
patch recently commited by Tejas ([2]).
As I looked, I realised that the ARM target and the AArch64 target
now differ drastically in how their Advanced SIM
As per RichardS's comment on the checkin to change the patterns for
_shiftsi here.
https://gcc.gnu.org/ml/gcc-patches/2014-05/msg02534.html
I toyed with the idea of removing this check but on balance it's
probably safe to have this to have the condition fail before the
recognizer kicks in.
Hi,
Now we have everything we need to start keeping track of the correct
"qualifiers" for each Neon builtin class in the arm back-end.
Some of the ARM Neon itypes are redundant when mapped to the qualifiers
framework. For now, don't change these, we will clean them up in patch
8 of the series.
Hi,
If we want to move all the code relating to "builtin" initialisation and
expansion to a common file, we must share the processor flags with that
common file.
This patch pulls those definitions out to config/arm/arm-protos.h
Bootstrapped and regression tested in series, and in isolation with
Hi,
These macros can always be defined as a base case of VAR1 and a "recursive"
case of VAR. At the moment, the body of VAR1 is duplicated to each
macro.
This patch makes that change.
Regression tested on arm-none-linux-gnueabihf with no issues.
OK?
Thanks,
James
---
gcc/
2014-11-12 James
Hi,
The poly types end up going through the default mangler, but only
sometimes.
We don't want to change the mangling for poly types with the next patch in
this series, so add a test which should pass before and after.
I've checked that the new tests pass at this stage of the patch series,
and
Hi,
This patch wires up builtin initialisation similar to the AArch64 backend,
making use of the "qualifiers" arrays to decide on types for each builtin
we hope to initialise.
We could take an old snapshot of the qualifiers code from AArch64, but as
our end-goal is to pull in the type mangling c
Hi,
This final patch clears up the remaining data structures which we no
longer have any use for...
* "_QUALIFIERS" macros which do not name a distinct pattern of
arguments/return types.
* The neon_builtin_type_mode enum is not needed, we can map directly to
the machine_mode.
* The neon
Hi,
possible_placement_new checks if the structure is at least big enough to
hold the VPTR pointer. But it uses BITS_PER_WORD for pointer size,
which is incorrect for many ILP32 targets. This patch replaces it with
POINTER_SIZE. Tested on Linux/x32. OK for trunk?
Thanks.
H.J.
---
2014-11-12
On 12 Nov 15:34, Richard Biener wrote:
> > > Seems like Vlad introduced the conflicting type with
> > Okay, we're going to test our changes with patch in the bottom applied
> > both to kyukhin/gomp4-offload and trunk.
> >
> > * gcc/lra-lives.c (struct bb_data): Rename to ...
> > (struct
OK.
Jason
>
> I don't think you have addressed all of the comments I made in the
> comment, do you?
>
> Regards,
> Kai
>
I added the three checks, if TARGET_PECOFF is defined, and fixed the
whitespace issues.
For the questions regarding C-runtime/Win32 functions I haven't changed
anything in the patch b
Hello!
2014-11-12 Uros Bizjak
* gcc.target/i386/pr45852.c: Simplify target selector.
* gcc.target/i386/pr63495.c: Ditto.
* gcc.target/i386/pr39496.c: Ditto.
* gcc.target/i386/pr36613.c: Ditto.
Tested on x86_64-linux-gnu {,-m32} and committed.
Uros.
Index: gcc.target/i386/pr45
On 12 November 2014 15:35, Alan Lawrence wrote:
> Nice! One nit - can the extra "tree" argument be a "const_tree" ? - I'll
> defer to the maintainers on the use of C++ default arguments in the AArch64
> backend. But LGTM.
Thanks, good catch.
The default parameter will go away once all of the cal
In response to https://gcc.gnu.org/ml/gcc-patches/2014-09/msg01803.html, this
series removes the VEC_RSHIFT_EXPR, instead using a VEC_PERM_EXPR (with a second
argument full of constant zeroes) to represent the shift.
I've kept the use of vec_shr optab for platforms that define it, as even on
p
This is a preliminary to patch 2, which wants functionality equivalent to
vect_gen_perm_mask (converting a char* to an RTL const_vector) but without the
check of can_vec_perm_p.
All existing calls to vect_gen_perm_mask barring that in perm_mask_for_reverse,
assert the return value is non-null.
This makes the vectorizer use VEC_PERM_EXPRs when doing reductions via shifts,
rather than VEC_RSHIFT_EXPR.
VEC_RSHIFT_EXPR presently has an endianness-dependent meaning (paralleling
vec_shr_optab). While the overall destination of this patch series is to make
these endianness-neutral, this pa
Hi!
On Tue, 5 Aug 2014 08:22:50 -0700, Cesar Philippidis
wrote:
> On 07/29/2014 02:07 AM, Thomas Schwinge wrote:
>
> > On Thu, 20 Mar 2014 15:42:48 +0100, I wrote:
> >> On Tue, 18 Mar 2014 14:50:44 +0100, I wrote:
> >>> On Tue, 18 Mar 2014 16:37:24 +0400, Ilmir Usmanov
> >>> wrote:
> Thi
This patch introduces TYPE_OVERFLOW_SANITIZED predicate to
consolidate a common check.
Bootstrapped/regtested on x86_64-linux, ok for trunk?
2014-11-12 Marek Polacek
* tree.h (TYPE_OVERFLOW_SANITIZED): Define.
* fold-const.c (fold_binary_loc): Use it.
* match.pd: Likew
On Tue, Nov 11, 2014 at 5:13 AM, Richard Biener wrote:
>
> This merges patterns from associate_plusminus and adjusts them with
> details from their fold-const.c pendants. It also fixes missing
> flag_sanitize checks on negate contraction on the way.
>
> This shows places where folds STRIP_NOPs wa
Tested (with patches 1+2):
Bootstrap + check-gcc on x64-none-linux-gnu
cross-tested check-gcc on aarch64-none-elf and aarch64_be-none-elf as these
platforms stand (i.e. without vec_shr_optab).
also cross-tested check-gcc on aarch64-none-elf and aarch64_be-none-elf after
applying https://gcc.
This redefines vec_shr optab to be the same (in terms of gcc vectors) regardless
of target endianness. The vectorizer uses this to do reductions via shifts, so
also change the vectorizer to shift things always the same way (from the
midend's POV of vectors).
cross-tested check-gcc on (1) aarch
On 12/11/14 14:56 +, Christopher Jefferson wrote:
I did suggest this change, so I feel I should defend it!
Our testing of many algorithms is woefully slim, that is how (for
example) the segfaulting bug in std::nth_element got through into a
release -- the tests for that algorithm were terrib
We make assumptions in the codebase about when the GC can run, and when
it can't (e.g. within numerous passes) but these aren't captured in a way
that's verifiable.
This patch introduces macros GGC_{BEGIN|END}_ASSERT_NO_COLLECTIONS for
marking regions of code where we assume that a GC can't happen
On 6 November 2014 10:19, Alan Lawrence wrote:
> This generates out-of-range errors at compile- (rather than assemble-)time
> for the vqdm*_lane intrinsics, and also provides a single place to do
> bigendian lane-swapping for all those intrinsics (and others to follow in
> later patches). This all
On 2014.11.05 at 18:32 +0100, Manuel López-Ibáñez wrote:
>
> I committed this as r217149.
This patch causes kernel build failures when using GCC_COMPARE_DEBUG=1.
"GCC_COMPARE_DEBUG=1 make CC=/var/tmp/gcc_trunk/usr/local/bin/gcc" is
enough to reproduce.
See: https://gcc.gnu.org/bugzilla/show_bug
On Nov 12, 2014, at 6:09 AM, Marek Polacek wrote:
> The following patch moves the path prunning code into a separate
> procedure and fixes the failures.
>
> Ok for trunk?
Ok.
Hello!
It's kind of obvious which targets are processed in gcc.target/i386
directory, so:
-/* { dg-skip-if "" { i?86-*-* x86_64-*-* } { "-march=*" } { "-march=k8" } } */
+/* { dg-skip-if "" { *-*-* } { "-march=*" } { "-march=k8" } } */
2014-11-12 Uros Bizjak
* gcc.target/i386/387-1.c (dg
2014-11-12 18:45 GMT+01:00 Patrick Wollgast :
>>
>> I don't think you have addressed all of the comments I made in the
>> comment, do you?
>>
>> Regards,
>> Kai
>>
>
> I added the three checks, if TARGET_PECOFF is defined, and fixed the
> whitespace issues.
>
> For the questions regarding C-runtime
On 12-11-14 15:17, Richard Biener wrote:
On Wed, 12 Nov 2014, Tom de Vries wrote:
[ moved from gcc@ to gcc-patches@ ]
[ subject was: Re: [gomp4] openacc kernels directive support ]
On 30-09-14 15:37, Tom de Vries wrote:
I would be happily accepting splitting the current autopar pass
that way,
Tobias Burnus wrote:
Now that CLooG is no longer used by GCC, it makes sense to also remove it from
the main configure file. Especially as the in-tree build currently only works
if also CLooG is available.
Turned out that I missed a dependency. One previously had all-gcc ->
depends on all-cloo
Have run check-gcc on gcc110.fsffrance.org (powerpc64-unknown-linux-gnu) using
this snippet on top of original patch; no regressions.
Alan Lawrence wrote:
So I'm no expert on RS6000 here, but following on from Segher's observation
about the change in pattern...so the difference in 'expand' is e
Pushed as r217440, also with Charles' whitespace fixes ('' -> tab) -
good spot!
Cheers, Alan
Marcus Shawcroft wrote:
On 6 November 2014 10:19, Alan Lawrence wrote:
This generates out-of-range errors at compile- (rather than assemble-)time
for the vqdm*_lane intrinsics, and also provi
On Wed, Nov 12, 2014 at 9:55 AM, H.J. Lu wrote:
> On Tue, Nov 11, 2014 at 5:13 AM, Richard Biener wrote:
>>
>> This merges patterns from associate_plusminus and adjusts them with
>> details from their fold-const.c pendants. It also fixes missing
>> flag_sanitize checks on negate contraction on t
Moore, Catherine writes:
> The patch looks good. Please fix up these couple of nits prior to
> committing.
OK, thanks for the second read through. One further amendment below, I'll
aim to commit later today.
> Index: gcc/config/mips/mips.c
> ===
On Wed, Nov 12, 2014 at 03:26:35AM -0600, Segher Boessenkool wrote:
> On Tue, Nov 11, 2014 at 08:27:22PM -0500, Michael Meissner wrote:
> > > Before the patch, the final reduction used *vsx_reduc_splus_v2df; after
> > > the patch, it is *vsx_reduc_plus_v2df_scalar. The former does a vector
> > > a
> -Original Message-
> From: Matthew Fortune [mailto:matthew.fort...@imgtec.com]
> Sent: Wednesday, November 12, 2014 1:59 PM
> To: Moore, Catherine; 'gcc-patches@gcc.gnu.org' (gcc-
> patc...@gcc.gnu.org); Eric Christopher (echri...@gmail.com)
> Cc: Richard Sandiford; Rich Fuhler; Rozycki
> (for MIPS) https://gcc.gnu.org/ml/gcc-patches/2014-09/msg01481.html,
> although I have not been able to test this as there doesn't seem to be
> any working MIPS/Loongson hardware in the Compile Farm;
I will post a patch to remove vec_shl and only support vec_shr for
little endian. This is on the
These issues just became DRs in Urbana.
Tested x86_64-linux, committed to trunk.
The other new DRs we need to make changes for are 2212 (to shuffle
some code between headers), 2217 (which I sent an email about earlier)
and 2354 (adding some new insert overloads in RB trees).
commit 5930336c2050
101 - 200 of 275 matches
Mail list logo
