> Jakub already wrote the invoke.texi part:
> http://gcc.gnu.org/ml/gcc-patches/2013-11/msg02061.html
Ah, thanks, I somehow missed it. When will this end up in trunk? I have
a depending patch.
-Y
Hi,
now that slim-lto objects are enabled by default, it would be nice to
use them when building gcc with bootstrap-lto. The following patch
implements the handling of these objects in gcc's build machinery.
(Once -fuse-linker-plugin is made the default, -ffat-lto-objects in
config/bootstrap-lto.m
On Wed, Nov 20, 2013 at 09:28:48AM +0400, Yury Gribov wrote:
> >>This patch adds support for -fsanitize=leak and -static-liblsan options.
> >>...
> >
> >Documentation?
> >
> >Ian
>
> In case this is a prereq for commit, here is a simple addition to invoke.texi.
Jakub already wrote the invoke.texi
I committed this as revision 205090 on behalf of Joshua.
Cheers,
Manuel.
On 15 November 2013 05:15, Joshua J Cogliati wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> The patch is the same as before (but for newer revision 204343 so line
> numbers are a bit different), but the copyr
Am 20.11.2013 06:00, schrieb Philippe Baril Lecavalier:
+If you do not have commit access, please send an email to mailto:gcc-patches@gcc.gnu.org";>gcc-patches@gcc.gnu.org
+and CC mailto:ger...@pfeifer.com";>ger...@pfeifer.com,
+with the following:
+
+
+ Secify [docs] in the subject header.
On 11/19/13 15:35, Miro Kropáček wrote:
Hello,
here's a patch against trunk which fixes the issue
(http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59196).
Regards,
Miro
gcc-56196.patch
Index: gcc/config/m68k/m68k.c
===
--- gcc/conf
> This patch is supposed to fix PR59063
(http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59063).
>
> The original bug results from libasan providing clock_gettime wrapper
and then trying to call the "real" clock_gettime.
> The "real" symbol is supposed to come from librt.so which was not
necessaril
This patch adds support for -fsanitize=leak and -static-liblsan options.
...
Documentation?
Ian
In case this is a prereq for commit, here is a simple addition to invoke.texi.
-Y
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 7074a48..960df85 100644
--- a/gcc/doc/invoke.texi
++
On 11/19/13 19:33, David Malcolm wrote:
FWIW, it looks like you attached the whitespace cleanup patch again,
rather than the one you discuss above.
For the archives, it looks like your email is referring to r205074
(though that itself seems to have some purely whitespace fixes, together
with th
Enclosed is a patch modifying three broken links, on three separate
pages. I also added some indications to about.html on how to submit a
patch for the web site for those who do not have commit access, which is
precisely what I have been instructed to do (so now it becomes
documented).
See
I've committed the attached to trunk as r205086, implementing support in
gdb for prettyprinting gcc's vec<>* types.
commit 0c55e3277d41a47e23178d05c6779a683145febd
Author: David Malcolm
Date: Tue Nov 19 22:18:54 2013 -0500
gdbhooks.py: Implement a prettyprinter for vec<>*
gcc/
I've committed the following to trunk as r205085, as a mixture of
enabling work towards gdb being able to print vec<>, and to fix issues
where the string-matching logic got confused by typedefs (done in a
rather crude way, by supporting multiple strings in the match, but it
works).
commit 0ac97497
On Tue, Nov 19, 2013 at 7:01 AM, Richard Biener wrote:
>
> $subject - the following turns
>
> loop_iterator li;
> FOR_EACH_LOOP (li, loop, LI_ONLY_INNERMOST)
>{
> ...
> if ()
>FOR_EACH_LOOP_BREAK;
>}
>
> into
>
> FOR_EACH_LOOP (loop, LI_ONLY_INNERMOST)
>{
> ..
Ping.
BR,
Terry
> -Original Message-
> From: gcc-patches-ow...@gcc.gnu.org [mailto:gcc-patches-
> ow...@gcc.gnu.org] On Behalf Of Terry Guo
> Sent: Wednesday, November 06, 2013 2:11 PM
> To: gcc-patches@gcc.gnu.org
> Cc: Richard Earnshaw; Ramana Radhakrishnan
> Subject: [Patch, ARM] New f
On Tue, 2013-11-19 at 18:55 -0700, Jeff Law wrote:
> So when we first started looking at the FSA/FSM optimization for
> coremark, I speculated that it could be done in the jump threader and
> that by doing so we'd see benefits in more general codes.
>
> This patch enables the code to allow multi
So when we first started looking at the FSA/FSM optimization for
coremark, I speculated that it could be done in the jump threader and
that by doing so we'd see benefits in more general codes.
This patch enables the code to allow multiple duplicated blocks on a
threading path. It won't catc
One small thing that I have not done that Jakub and several other
have asked me before is that, there are no tests in c-c++-common for
_Cilk_for. The reason being that the syntax between C and C++
implementations are different. In C++, the induction variable must be
defined in the initializer (e
No functional changes. Just cleaning up trailing whitespace that I saw.
Installed on the trunk.
* tree-ssa-threadupdate.c: Fix trailing whitespace.
* tree-ssa-threadupdate.h: Likewise.
diff --git a/gcc/tree-ssa-threadupdate.c b/gcc/tree-ssa-threadupdate.c
index afd7ac4..1b7c73
Hi,
The issue files in PR 57683 include lra-constraints.o,
lra-eliminations.o and tree-switch-conversion.o.
Jeff had fixed them in trunk (r197467 and r198999):
http://gcc.gnu.org/ml/gcc-patches/2013-05/msg00957.html
http://gcc.gnu.org/ml/gcc-patches/2013-04/msg00211.html
Can we backport the two
On Tue, Nov 19, 2013 at 5:02 PM, Rong Xu wrote:
> Hi all,
>
> I merged this old patch with current trunk. I also make the following changes
> (1) not using weak references. Now every *profile_atomic() has it's
> own .o so that none of them will be in the final binary if
> -fprofile-generate-atomic
On Nov 19, 2013, at 2:52 PM, Joseph S. Myers wrote:
> If a bound violation should be detected, the test should PASS when it's
> detected and FAIL when it's not, rather than XFAILing and XPASSing.
> Hopefully dg-shouldfail will do the right thing (causing an error exit
> status from the test to
On Nov 19, 2013, at 2:05 PM, Ilya Enkovich wrote:
>> Anything added that's XFAILed should have a comment explaining the reason
>> for the XFAILing (a reference to a bug in GCC Bugzilla is a good idea,
>> with that bug then mentioning the particular test that indicates whether
>> the bug is still p
Hi all,
I merged this old patch with current trunk. I also make the following changes
(1) not using weak references. Now every *profile_atomic() has it's
own .o so that none of them will be in the final binary if
-fprofile-generate-atomic is not specified.
(2) more value profilers have the atomic
Here is a little one that was useful in debugging during wide-int development,
but isn't dependent upon wide-int.
Committed.
* gdbinit.in: Add pmz to print out mpz values.
Index: gdbinit.in
===
--- gdbinit.in (revision 20
On Tue, Nov 19, 2013 at 1:45 AM, Richard Biener wrote:
>
> On Mon, 18 Nov 2013, Cong Hou wrote:
>
> > I tried your method and it works well for doubles. But for float,
> > there is an issue. For the following gimple code:
> >
> >c1 = a - b;
> >c2 = a + b;
> >c = VEC_PERM
> >
> > It ne
On Tue, Nov 19, 2013 at 5:41 PM, Bill Schmidt
wrote:
> Hi,
>
> When possible, we translate VEC_PERM_EXPRs into vector splat operations.
> A previous patch fixed this up for little endian, but there was an
> oversight for V16QI mode. This patch fixes that oversight. This fixes
> the failing test
I found a few tests containing VERIFY assertions that were incorrectly
marked { dg-do compile } so weren't executed, hiding some broken tests
and a missing export. This adds the export and fixes the tests. I
deleted the TR1 test because it won't link due to unimplemented
features so doesn't really
On Tue, 19 Nov 2013, Joseph S. Myers wrote:
> No, they should use { dg-add-options mpx } (well, both the directory name
> and the dg-add-options argument should use whatever generic name for this
> functionality we ended up with, rather than the name for the particular
> instance of it on x86,
On Wed, 20 Nov 2013, Ilya Enkovich wrote:
> 2013/11/20 Joseph S. Myers :
> > On Wed, 20 Nov 2013, Ilya Enkovich wrote:
> >
> >> Here is a patch to add MPX tests.
> >
> > I don't think these should be under gcc.target/i386; gcc.dg/mpx would be
> > better, so if someone adds a corresponding feature
On 19 Nov 12:02, Jeff Law wrote:
> On 11/18/13 14:03, Ilya Enkovich wrote:
> >2013/11/19 Jeff Law :
> >>On 11/18/13 12:16, Ilya Enkovich wrote:
> >>>
> >>>With current recursion elimination we will have:
> >>>
> >>>test (int *param1)
> >>>{
> >>>:
> >>>
> >>>:
> >>>_7 = PHI
> >>>bounds2 = _
Hi,
When possible, we translate VEC_PERM_EXPRs into vector splat operations.
A previous patch fixed this up for little endian, but there was an
oversight for V16QI mode. This patch fixes that oversight. This fixes
the failing test gcc.dg/torture/vshuf-v16qi.c.
Bootstrapped and tested on powerpc
Hello,
here's a patch against trunk which fixes the issue
(http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59196).
Regards,
Miro
gcc-56196.patch
Description: Binary data
On Tue, Nov 19, 2013 at 9:40 AM, Jeff Law wrote:
> On 11/19/13 10:24, Teresa Johnson wrote:
>>
>> On Tue, Nov 19, 2013 at 7:44 AM, Jan Hubicka wrote:
>>>
>>> Martin,
>>> can you, please, generate the updated systemtap with
>>> -freorder-blocks-and-partition enabled?
>>>
>>> I am in favour of enab
> -Original Message-
> From: Jakub Jelinek [mailto:ja...@redhat.com]
> Sent: Tuesday, November 19, 2013 12:00 PM
> To: Iyer, Balaji V
> Cc: Joseph S. Myers; gcc-patches@gcc.gnu.org; Aldy Hernandez
> (al...@redhat.com); Jeff Law
> Subject: Re: [GOMP4] [PATCH] SIMD-Enabled Functions (former
This adds { dg-do compile } to some tests that only use static_assert
and adjusts the swap overloads so that all commented-out assertions
can be enabled.
2013-11-19 Jonathan Wakely
* testsuite/23_containers/forward_list/allocator/noexcept.cc: Change
to compile-only test. Adjust
2013/11/20 Joseph S. Myers :
> On Wed, 20 Nov 2013, Ilya Enkovich wrote:
>
>> Here is a patch to add MPX tests.
>
> I don't think these should be under gcc.target/i386; gcc.dg/mpx would be
> better, so if someone adds a corresponding feature for another target,
> they don't need to move all the tes
On Wed, 20 Nov 2013, Ilya Enkovich wrote:
> Here is a patch to add MPX tests.
I don't think these should be under gcc.target/i386; gcc.dg/mpx would be
better, so if someone adds a corresponding feature for another target,
they don't need to move all the tests around.
Anything added that's XFAI
Basile,
The patch fixes most of the plugin failures except:
FAIL: g++.dg/plugin/selfassign.c compilation
The error is
/opt/gcc/work/gcc/testsuite/g++.dg/plugin/selfassign.c: In function 'void
warn_self_assign(gimple)':
/opt/gcc/work/gcc/testsuite/g++.dg/plugin/selfassign.c:227:75: error:
'may
On 19 November 2013 21:44, David Edelsohn wrote:
> The libstdc++ 17_intro/static.cc elicits multi-line AIX linker
> warnings about TOC reload instructions. This patch adds dg-prune
> directives to ignore the warnings and allow the testcase to pass.
>
> Okay?
Yes, thanks.
On Tue, 2013-11-19 at 20:33 +0100, Dominique Dhumieres wrote:
> > Thanks: Committed revision 205038.
>
> This seems to break several g++ tests: see
> http://gcc.gnu.org/ml/gcc-testresults/2013-11/msg01482.html
> On x86_64-apple-darwin13, the ICE is
>
> cc1: error: cannot load plugin ./one_time_p
Do I understand correctly that this will require changes to other
toolchain components such as glibc and newlib where they use some
particular list of __ARM_ARCH_7*__ macros to detect v7 (or some subset of
v7 such as v7-A or v7-A/v7-R) - but not if they use __ARM_ARCH when that
is defined, beca
Basile,
http://gcc.gnu.org/ml/gcc-testresults/2013-11/msg01482.html is for
x86_64-unknown-linux-gnu. However I cannot infer from the pointer
what is the ICE. Nevertheless I'll try your patch.
Thanks for the answer.
Dominique
The libstdc++ 17_intro/static.cc elicits multi-line AIX linker
warnings about TOC reload instructions. This patch adds dg-prune
directives to ignore the warnings and allow the testcase to pass.
Okay?
Thanks, David
* testsuite/17_intro/static.cc: Ignore AIX TOC reload warnings.
Index: te
On Tue, 2013-11-19 at 20:33 +0100, Dominique Dhumieres wrote:
> > Thanks: Committed revision 205038.
>
> This seems to break several g++ tests: see
> http://gcc.gnu.org/ml/gcc-testresults/2013-11/msg01482.html
> On x86_64-apple-darwin13, the ICE is
I would guess that the following trivial patch
On Tue, 2013-11-19 at 20:33 +0100, Dominique Dhumieres wrote:
> > Thanks: Committed revision 205038.
>
> This seems to break several g++ tests: see
> http://gcc.gnu.org/ml/gcc-testresults/2013-11/msg01482.html
> On x86_64-apple-darwin13, the ICE is
>
> cc1: error: cannot load plugin ./one_time_p
On Tue, Nov 19, 2013 at 1:22 AM, Marcus Shawcroft
wrote:
> On 13 November 2013 00:04, Andrew Pinski
>
> wrote:
>>
>> Hi all,
>> This patch implements the trap pattern for the AARCH64 back-end. I
>> used the "brk #0" instruction as that is the breakpoint instruction
>> that GDB uses. I looked
> 2013-11-13 Cary Coutant
>
> gcc/cp/
> * mangle.c (to_base36): New function.
> (dump_substitution_candidates): Add checks for NULL.
> Print substitution index in base 36.
Ping?
-cary
On Tue, Nov 19, 2013 at 10:09 AM, Michael Matz wrote:
> OMG, finally a c++ification that _shrinks_ client code instead of
> bloating it.
Not quite. The patch that converted VEC macros removed a non-trivial
amount of client code.
$ git log -p -n1 f1f41a6cdc47d5123dd30ab110cc35c90f8189cb -- $(fin
On Tue, Nov 19, 2013 at 1:00 PM, Andi Kleen wrote:
> Teresa Johnson writes:
>
>> This patch enables -freorder-blocks-and-partition by default for x86
>> at -O2 and up. It is showing some modest gains in cpu2006 performance
>> with profile feedback and -O2 on an Intel Westmere system. Specifically
On Tue, Nov 19, 2013 at 1:47 PM, Mike Stump wrote:
> On Nov 19, 2013, at 8:54 AM, Ulrich Weigand wrote:
>> another test case fix: darwin-longlong.c implements a "msw" routine
>> extracting the most significant word from a long long. This of course
>> needs to be updated for little-endian ...
>>
Teresa Johnson writes:
> This patch enables -freorder-blocks-and-partition by default for x86
> at -O2 and up. It is showing some modest gains in cpu2006 performance
> with profile feedback and -O2 on an Intel Westmere system. Specifically,
> I am seeing consistent improvements in 401.bzip2 (1.5-
Hi,
Here is a patch to support instrumentation in vararg expands for i386 target.
Thanks,
Ilya
--
2013-11-19 Ilya Enkovich
* config/i386/i386.c (setup_incoming_varargs_64): Store
bounds for each stored register.
(ix86_va_start): Initialize bounds for pointers in va_lis
Hi,
Here is a patch to support MPX ABI
(http://software.intel.com/en-us/articles/linux-abi).
Thanks,
Ilya
--
2013-11-13 Ilya Enkovich
* config/i386/i386.c (x86_64_reg_class): Add
X86_64_BOUNDED_INTEGER_CLASS and
X86_64_BOUNDED_INTEGERSI_CLASS.
(ix86_return_pop
On 18 Nov 22:00, Uros Bizjak wrote:
> Hello!
>
> > Here is a patch to add size relocation and instruction to obtain object's
> > size in i386 target.
>
> +(define_insn "move_size_reloc_"
> + [(set (match_operand:SWI48 0 "register_operand" "=r")
> +(match_operand: 1 "size_relocation" "Z"
On 19 Nov 12:33, Jeff Law wrote:
> On 11/19/13 05:13, Ilya Enkovich wrote:
> >On 19 Nov 13:00, Richard Biener wrote:
> >>I'd say not in the gimplifier either but in varpool (symbol table) code
> >>where the symbols are ultimatively registered with?
> >
> >Something like that?
> >
> >--- a/gcc/varpo
2013/11/19 Jeff Law :
> On 11/19/13 05:20, Ilya Enkovich wrote:
>>
>> 2013/11/19 Richard Biener :
>>>
>>> On Mon, Nov 18, 2013 at 8:12 PM, Ilya Enkovich
>>> wrote:
2013/11/18 Jeff Law :
>
> On 11/18/13 11:27, Ilya Enkovich wrote:
>>
>>
>>
>> How does pointer passe
I have some small comments to the patch:
* You should also update gcc/doc/invoke.texi
Sergey Ostanevich wrote:
index 0026683..84911a0 100644
--- a/gcc/c-family/c.opt
+++ b/gcc/c-family/c.opt
...
+Wopenmp-simd
+C C++ Var(openmp_simd) Warning
+Warn about omp simd construct is overridden by cost
On 11/18/13 03:45, Ilya Enkovich wrote:
Hi,
Here is a patch remove bounded params from candidates for reduction.
Thanks,
Ilya
--
2013-11-15 Ilya Enkovich
* tree-sra.c: Include tree-chkp.h.
(find_param_candidates): Bounded param is not
a candidate.
OK.
jeff
> Thanks: Committed revision 205038.
This seems to break several g++ tests: see
http://gcc.gnu.org/ml/gcc-testresults/2013-11/msg01482.html
On x86_64-apple-darwin13, the ICE is
cc1: error: cannot load plugin ./one_time_plugin.so
dlopen(./one_time_plugin.so, 10): image not found
/opt/gcc/work/gcc
On 11/19/13 05:13, Ilya Enkovich wrote:
On 19 Nov 13:00, Richard Biener wrote:
On Mon, Nov 18, 2013 at 5:45 PM, Jeff Law wrote:
On 11/08/13 02:02, Ilya Enkovich wrote:
Hi,
Here is an updated patch version with no langhook.
Regarding TLS objects issue - I do not think compiler should compen
On 11/19/13 05:00, Richard Biener wrote:
On Mon, Nov 18, 2013 at 5:45 PM, Jeff Law wrote:
On 11/08/13 02:02, Ilya Enkovich wrote:
Hi,
Here is an updated patch version with no langhook.
Regarding TLS objects issue - I do not think compiler should compensate
the absence of instrumentation in
On 11/18/13 12:12, Ilya Enkovich wrote:
2013/11/18 Jeff Law :
On 11/18/13 11:27, Ilya Enkovich wrote:
How does pointer passed to regular function differ from pointer passed
to splitted function? How do I know then which pointer is to be passed
with bounds and wchich one is not? Moreover curre
On 11/18/13 12:12, Ilya Enkovich wrote:
2013/11/18 Jeff Law :
On 11/18/13 11:27, Ilya Enkovich wrote:
How does pointer passed to regular function differ from pointer passed
to splitted function? How do I know then which pointer is to be passed
with bounds and wchich one is not? Moreover curre
ok, got it.
I'm not sure if C/C++ and FORTRAN are enough?
* common.opt: Added new option -fsimd-cost-model
* tree-vectorizer.h (unlimited_cost_model): Interface update
to rely on particular loop info
* tree-vect-data-refs.c (vect_peeling_hash_insert): Update to
On 11/19/13 05:20, Ilya Enkovich wrote:
2013/11/19 Richard Biener :
On Mon, Nov 18, 2013 at 8:12 PM, Ilya Enkovich wrote:
2013/11/18 Jeff Law :
On 11/18/13 11:27, Ilya Enkovich wrote:
How does pointer passed to regular function differ from pointer passed
to splitted function? How do I know
On 11/19/13 07:06, Ilya Enkovich wrote:
Hi,
Here is a patch to add flag for marking symbols as requiring static
initialization of bounds. Used by Pointer Bounds Checker to handle statically
initialized pointers and static bounds vars.
Thanks,
Ilya
--
2013-11-19 Ilya Enkovich
* cg
In PR 59195, I describe a demangler problem with parsing
conversion operators that have template parameters:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59195
For example,
$ c++filt _ZN1AcvPT_I1CEEv
fails -- it should print "A::operator C*()".
$ c++filt _ZN1AcvT_IiEI1CEEv
prints "A::ope
On 11/18/13 14:03, Ilya Enkovich wrote:
2013/11/19 Jeff Law :
On 11/18/13 12:16, Ilya Enkovich wrote:
With current recursion elimination we will have:
test (int *param1)
{
:
:
_7 = PHI
bounds2 = __builtin_arg_bounds (_7) -- WRONG
I wouldn't say it's wrong. It's conservatively corr
"Joseph S. Myers" writes:
> On Tue, 19 Nov 2013, Gaius Mulley wrote:
>
> We don't use --enable- options like that. Instead:
>
> (a) The front end's config-lang.in file sets target_libs, thereby causing
> the library to be disabled if the language is. Of course this means you
> don't actually
On 11/19/13 05:00, Richard Sandiford wrote:
The (x >> c) << c folding has:
&& tree_fits_shwi_p (arg1)
&& TREE_INT_CST_LOW (arg1) < prec
&& tree_fits_shwi_p (TREE_OPERAND (arg0, 1))
&& TREE_INT_CST_LOW (TREE_OPERAND (arg0, 1)) < prec)
At first glance the u
On Nov 19, 2013, at 8:54 AM, Ulrich Weigand wrote:
> another test case fix: darwin-longlong.c implements a "msw" routine
> extracting the most significant word from a long long. This of course
> needs to be updated for little-endian ...
>
> Tested on powerpc64le-linux.
>
> OK for mainline?
My
On 11/19/13 09:43, Richard Earnshaw wrote:
PR 54300 is a problem in regcprop where the compiler sees
(parallel [(set (x) (y)
(set (y) (x)]) (REG_UNUSED (y))
as a single-set insn (since the other operand, y, is not used) and
replaces a use of x with a use of y. However, it fails to
Hello,
The attached patch fixes a typo in gcc/config/sh-c.c which was
introduced recently by some refactoring work. Committed as obvious as
rev 205052.
Cheers,
Oleg
gcc/ChangeLog:
* config/sh/sh-c.c: Fix typo in include of file attribs.h.
Index: gcc/config/sh/sh-c.c
On Mon, Nov 18, 2013 at 2:15 PM, Jan Hubicka wrote:
> Hi,
> this patch fixes problem we noticed with Martin Liska where gcov_dump is
> called
> several times per execution of firefox (on each fork and exec). This causes
> runs to be large and makes functions executed once per program to be
> co
On 11/19/13 10:32, Steven Bosscher wrote:
Yes. In the GCC3 days it was important for sincos on i386, and on mk68
it used to be important for some of the funnier patterns. Not sure if
it's still useful today, though. Might be worth looking into, just to
avoid the confusion in the future.
I doubt
Hi,
I was looking at some scheduler dumps and spotted that
the pattern "zero_extenddi2" is missing a type attribute
on ARM.
I've fixed that with this obvious patch, committed as
revision 205050.
Tested on arm-none-eabi with no regressions.
Thanks,
James
---
gcc/
2013-11-19 James Greenhalgh
On 11/19/13 10:24, Teresa Johnson wrote:
On Tue, Nov 19, 2013 at 7:44 AM, Jan Hubicka wrote:
Martin,
can you, please, generate the updated systemtap with
-freorder-blocks-and-partition enabled?
I am in favour of enabling this - it is usefull pass and it is pointless ot
have passes that are not
söndag 17 november 2013 22.37.08 skrev Magnus Granberg:
> lördag 16 november 2013 20.37.58 skrev Ryan Hill:
> > On Wed, 13 Nov 2013 23:28:45 +0100
> >
> > Magnus Granberg wrote:
> > > Hi
> > > This patchset will add a new configure options --enable-default-pie.
> > > With the new option enable
Chung-Lin Tang writes:
>>> +;; Integer logical Operations
>>> +
>>> +(define_code_iterator LOGICAL [and ior xor])
>>> +(define_code_attr logical_asm [(and "and") (ior "or") (xor "xor")])
>>> +
>>> +(define_insn "si3"
>>> + [(set (match_operand:SI 0 "register_operand" "=r,r,r")
>>> +
On Tue, Nov 19, 2013 at 6:27 PM, Jeff Law wrote:
> I don't remember the history here, but that may have been to better support
> divmod and similar insns.
Yes. In the GCC3 days it was important for sincos on i386, and on mk68
it used to be important for some of the funnier patterns. Not sure if
it
Hi all,
This patch will add support armv7ve to gcc. Armv7ve is basically a
armv7-a architecture profile with Virtualization Extensions. Additional
test cases are added.
With this patch and to keep backward compatibility with old assembler,
the following asm header will be generated when -mar
Hi,
This patch fixes vdiv[q]_f[32,64] neon intrinsics testcase.
Testcase ran on both little and big endian targets with no problems.
OK?
Thanks,
Alex
gcc/testsuite/
2013-11-19 Alex Velenko
* gcc.target/aarch64/vdiv_f.c (test_vdiv_f32): vector indexing
replaced with builtins.
On Tue, Nov 19, 2013 at 7:08 AM, Diego Novillo wrote:
> On Tue, Nov 19, 2013 at 9:48 AM, Ian Lance Taylor wrote:
>> Hi, as noted in gcc/go/README.gcc, the files in gcc/go/gofrontend are
>> actually mirrored from a different repository. Please do not directly
>> commit changes to those files. In
Hi,
This patch makes testcase for vneg[q]_s[8,16,32,64] big-endian safe.
vneg_s.c testcase ran with both big and little endian compilers with no
problems.
is patch OK?
Thanks,
Alex
gcc/testsuite/
2013-11-19 Alex Velenko
* gcc.target/aarch64/vneg_s.c (test_vneg_s8): fixed to not us
On Tue, Nov 19, 2013 at 5:31 AM, Yuri Rumyantsev wrote:
> Hi All,
>
> We found out that compiler configured with '-fpmath=sse' option does
> not generate scalar floating-point instructions present in the SSE
> instruction set for generic32 that leads to performance degradation
> for Fortran benchm
> -Original Message-
> From: Jakub Jelinek [mailto:ja...@redhat.com]
> Sent: Tuesday, November 19, 2013 12:00 PM
> To: Iyer, Balaji V
> Cc: Joseph S. Myers; gcc-patches@gcc.gnu.org; Aldy Hernandez
> (al...@redhat.com); Jeff Law
> Subject: Re: [GOMP4] [PATCH] SIMD-Enabled Functions (former
On Tue, Nov 19, 2013 at 6:22 PM, Richard Earnshaw wrote:
>>> as a single-set insn (since the other operand, y, is not used) and
>>> replaces a use of x with a use of y. However, it fails to take into
>>> account that y has been clobbered in the insn itself.
>>
>> Ah, wait. Incorrect use of single_
On 11/19/13 10:17, Steven Bosscher wrote:
On Tue, Nov 19, 2013 at 5:43 PM, Richard Earnshaw wrote:
PR 54300 is a problem in regcprop where the compiler sees
(parallel [(set (x) (y)
(set (y) (x)]) (REG_UNUSED (y))
as a single-set insn (since the other operand, y, is not used) and
re
Committed with all your changes as revision 205049.
the only interesting change is the response to your last comment.
I changed the frag to:
/* Third, unsigned integers with top bit set never fit signed types. */
- if (!TYPE_UNSIGNED (type) && sgn_c == UNSIGNED && wi::neg_p (c))
-retur
On Tue, Nov 19, 2013 at 7:44 AM, Jan Hubicka wrote:
> Martin,
> can you, please, generate the updated systemtap with
> -freorder-blocks-and-partition enabled?
>
> I am in favour of enabling this - it is usefull pass and it is pointless ot
> have passes that are not enabled by default.
> Is there r
On 19/11/13 17:17, Steven Bosscher wrote:
> On Tue, Nov 19, 2013 at 5:43 PM, Richard Earnshaw wrote:
>> PR 54300 is a problem in regcprop where the compiler sees
>> (parallel [(set (x) (y)
>>(set (y) (x)]) (REG_UNUSED (y))
>>
>> as a single-set insn (since the other operand, y, is not
On 15/11/13 11:21, Eric Botcazou wrote:
> Hi,
>
> because the compiler still uses the legacy encodings for the VFP registers in
> DWARF, when for example d8 is saved onto the stack, the CFI records a save of
> s16. This is more or less correct in little-endian mode, but plain wrong in
> big-en
On Tue, Nov 19, 2013 at 5:43 PM, Richard Earnshaw wrote:
> PR 54300 is a problem in regcprop where the compiler sees
> (parallel [(set (x) (y)
>(set (y) (x)]) (REG_UNUSED (y))
>
> as a single-set insn (since the other operand, y, is not used) and
> replaces a use of x with a use of y.
> On Tue, Nov 19, 2013 at 1:42 PM, Jan Hubicka wrote:
> > The patch also removes simple peeling at RTL level that is mostly obsoleted
> > by
> > gimple level (in few cases in our testsuite the RTL code is able to
> > determine
> > loop bounds better than gimple code, but these seems to be just we
On 19/11/13 16:26, Joseph S. Myers wrote:
In any target header installed for user use, such as arm_acle.h, you need
to be namespace-clean. In this case, that means you need to use
implementation-namespace identifiers such as __a, __b and __d in case the
user has defined macros with names such as
On 19/11/13 16:48, Kyrill Tkachov wrote:
> Hi all,
>
> This patch improves the rtx costs computation for the add/sub + shift
> operations
> for modes narrower than SImode. There's a bit of refactoring going on, but
> essentially they are computed in the same way that SImode costs for these
> o
David Malcolm wrote:
>On Tue, 2013-11-19 at 09:49 +0100, Richard Biener wrote:
>> On Mon, 18 Nov 2013, David Malcolm wrote:
>>
>> > On Fri, 2013-11-15 at 20:38 -0500, David Malcolm wrote:
>> > > On Wed, 2013-11-13 at 14:44 +0100, Richard Biener wrote:
>> > > > On Wed, 13 Nov 2013, David Malcolm w
On Tue, Nov 19, 2013 at 04:54:29PM +, Iyer, Balaji V wrote:
> I just need a clarification, so I am sorry if I am making you repeat:
>
> Right now, the array of tokens (vec elem_fn_tokens) is passed in
> as a parameter and then passed back to the c_parser_declaration_or_fndef
> function.
>
> I
Hello,
another test case fix: darwin-longlong.c implements a "msw" routine
extracting the most significant word from a long long. This of course
needs to be updated for little-endian ...
Tested on powerpc64le-linux.
OK for mainline?
Bye,
Ulrich
ChangeLog:
* gcc.target/powerpc/darwin
> -Original Message-
> From: Jakub Jelinek [mailto:ja...@redhat.com]
> Sent: Tuesday, November 19, 2013 11:31 AM
> To: Joseph S. Myers
> Cc: Iyer, Balaji V; gcc-patches@gcc.gnu.org; Aldy Hernandez
> (al...@redhat.com); Jeff Law
> Subject: Re: [GOMP4] [PATCH] SIMD-Enabled Functions (former
1 - 100 of 237 matches
Mail list logo