Hi Maintainers,
Below patch adds register constraint "r" for destination operand in
"stack_protect_test" pattern.
We need a general register here and adding "r" will avoid vector
register getting allocated.
regression tested on aarch64-unknown-linux-gnu.
Ok for trunk?
regards,
Venkat.
gcc/Ch
On 03-09-14 18:58, Tom de Vries wrote:
I've build the patch and ran the fuse-caller-save tests, and I'm currently
bootstrapping and reg-testing it on x86_64.
Vladimir,
This patch fixes a problem (found on s390) in one of the committed
fuse-caller-save patches. s390 is the only user of the
I
Ping.
On Tue, Aug 26, 2014 at 10:41 AM, Andrey Turetskiy
wrote:
> Ping.
>
> On Tue, Aug 19, 2014 at 12:45 PM, Kirill Yukhin
> wrote:
>> Hello,
>> On 12 Aug 10:58, Andrey Turetskiy wrote:
>>> All remarks from
>>> https://gcc.gnu.org/ml/gcc-patches/2014-06/msg02166.html are fixed.
>>> Updated ver
Hi maintainers,
I just added "=r" and retested it.
gcc/ChangeLog
2014-09-04 Venkataramanan Kumar
* config/aarch64/aarch64.md (stack_protect_test_) Add register
constraint for operand 0.
diff --git a/gcc/config/aarch64/aarch64.md b/gcc/config/aarch64/aarch64.md
index b5be79c..ed6
On Thu, Sep 04, 2014 at 08:42:31AM +0100, Venkataramanan Kumar wrote:
> Hi maintainers,
>
> I just added "=r" and retested it.
I had a very similar patch to this sitting in my local tree. However,
I am surprised you have left operand 3 as an output operand. In my tree
I had marked operand 3 as "&
> On 09/02/2014 01:59 AM, Matthew Fortune wrote:
> >> > gcc/
> >> > * target.def (TARGET_DWARF_FRAME_REG_MODE): New target hook.
> >> > * targhooks.c (default_dwarf_frame_reg_mode): New function.
> >> > * targhooks.h (default_dwarf_frame_reg_mode): New prototype.
> >> > * doc/tm.texi.in (TARGET
Hi!
-Wlogical-not-parentheses was enabled recently via -Wall, and it
triggered for rx-elf
(http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=350506)
on a build with config-list.mk, where a GCC of the same revision is
used:
g++ -c -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-e
Hi,
As reported by pr62631, case ivopts-lt-2.c is failed on sparc64. The root
cause is shiftadd_cost calculated on sparc64 is huge which prevents gcc from
choosing the wanted candidate. The problem with IVOPT is it always assumes
that shiftadd_cost is smaller than the normal cost, while it's not
> Well, but that's a bug in the Ada frontend if it does exceptions behind
> GCCs back. ISTR that the middle-end also supports a SJLJ EH scheme?
No and yes respectively. As already explained multiple times, GNAT uses an
SJLJ scheme which is entirely managed by the front-end and (manually) lowere
On Thu, Sep 4, 2014 at 11:04 AM, Eric Botcazou wrote:
>> Well, but that's a bug in the Ada frontend if it does exceptions behind
>> GCCs back. ISTR that the middle-end also supports a SJLJ EH scheme?
>
> No and yes respectively. As already explained multiple times, GNAT uses an
> SJLJ scheme whi
On Thu, Sep 04, 2014 at 12:22:33PM +0200, Richard Biener wrote:
> But then the proposed patch pessimizes code too much IMHO.
Yeah. IMHO if Ada wants to __builtin_longjmp from synchronous signal handlers
(SIGFPE, SIGSEGV, ...) then the middle-end needs to be aware of that and
have it represented i
On Wed, Sep 3, 2014 at 7:54 PM, Aldy Hernandez wrote:
> [Jason, Richard]: Is it useful for my patches to contain ChangeLog entries?
> I find them mildly annoying for something that will inevitably be rewritten
> multiple times, but if it aids in reviewing my WIP, I am more than happy to
> continue
On Thu, Aug 21, 2014 at 4:05 PM, Marat Zakirov wrote:
>
> On 08/14/2014 05:40 PM, Marat Zakirov wrote:
>>
>>
>> On 08/07/2014 12:52 PM, Marat Zakirov wrote:
>>>
>>>
>>> On 07/31/2014 04:08 PM, Marat Zakirov wrote:
On 07/24/2014 07:40 PM, Marat Zakirov wrote:
>
>
> On 07/
The following two patches each fix PR63148, a wrong-code issue
caused by bogus array indices a-la
&global_data.b[(sizetype) i + 536870911] which have a correct
address when lowered but bogus index.
The case in question can be mitigated by disabling folding of
(sizetype) i * 8 + 4294967288 to ((si
On Wed, Sep 03, 2014 at 03:01:17PM +0930, Alan Modra wrote:
> In fact if you look at the corresponding location expression for
> -fno-section-anchors code you get something quite screwy too.
>
> 018f 0108 0114 (DW_OP_breg10 (r10): 0; DW_OP_addr: 144;
> DW_OP_plus; DW_OP_stack_value
>
On Thu, Sep 04, 2014 at 02:11:26PM +0200, Richard Biener wrote:
> Sofar I have only fully tested removing try_move_mult_to_index
> on trunk which has some fallout that I have fixed and some
> fallout that should be addressed as followup. The patch
Doesn't that regress e.g. testcases where users w
On Thu, 4 Sep 2014, Jakub Jelinek wrote:
> On Thu, Sep 04, 2014 at 02:11:26PM +0200, Richard Biener wrote:
> > Sofar I have only fully tested removing try_move_mult_to_index
> > on trunk which has some fallout that I have fixed and some
> > fallout that should be addressed as followup. The patch
From: Trevor Saunders
Hi,
subject says it all.
bootstrapped + regtested on x86_64-unknown-linux-gnu, and survived
config-list.mk with the next patch. I think Jeff will be happy to see the
as_a go away and so won't mind me taking this as pre approved also.
Trev
gcc/ChangeLog:
2014-09-04 Tre
From: Trevor Saunders
Hi,
subject says it all.
bootstrapped + regtested on x86_64-unknown-linux-gnu, and survived
config-list.mk with the next patch. This is pretty clearly within the pre
approval so will commit it later today unless someone complains.
Trev
gcc/ChangeLog:
2014-09-04 Trevor
On Wed, Sep 3, 2014 at 3:47 PM, Siva Chandra wrote:
> On Wed, Sep 3, 2014 at 3:35 PM, Jonathan Wakely wrote:
>> I was waiting to see which version of the patch actually works, so
>> that users can use the xmethods. There's no point committing the patch
>> if they aren't installed and can't be use
On Wed, Sep 3, 2014 at 11:22 PM, Jeff Law wrote:
> On 08/13/14 03:44, Richard Biener wrote:
>>
>>
>> I don't see that this pass should "scrog" a loop beyond repair. Btw,
>> the "proper" way of just fixing loops up (assuming that all loop
>> headers are still at their appropriate place) is to _jus
On Thu, Sep 4, 2014 at 5:41 AM, Kugan wrote:
>>> I added this part of the code (in cfgexpand.c) to handle binary/unary/..
>>> gimple operations and used the LHS value range to infer the assigned
>>> value range. I will revert this part of the code as this is wrong.
>>>
>>> I dont think checking pr
On Thu, Sep 4, 2014 at 5:58 AM, Andi Kleen wrote:
>>
>> Anyway, removing !optimize checks in favor of flag_no_inline checks
>> and initializing that properly is a cleanup as well.
>
> Patch looks good to me.
Unfortunately it doesn't pass bootstrap (inline-summary re-use
between IPA passes is a ma
Hi all,
This patch adds a Vim config (.local.vimrc) to root folder. This would
allow automatic setup of GNU formatting for C/C++/Java/Lex files in GCC
(similar to what we already have for Emacs via .dir-locals.el). The
formatting is borrowed from https://gcc.gnu.org/wiki/FormattingCodeForGCC
On Thu, Sep 04, 2014 at 02:57:47PM +0200, Richard Biener wrote:
> Note that I think we arrived at the point where the loop structure
> has annotations that are required for correctness :/ (simduid
> for example - if that goes away we do ...? ICE? generate
> wrong code? I don't know - Jakub shou
Hi!
On Tue, 2 Sep 2014 21:49:46 +0400, Ilya Verbin wrote:
> This patch allows to compile binaries with offloading without passing -flto
> option, and
> w/o performing link-time optimizations of the host code.
Thanks for working on this!
> How it works:
> 1. If there is at least one function o
On Thu, Sep 4, 2014 at 8:04 AM, Andi Kleen wrote:
>> No, not a new "fake" option either but just initialize
>> DECL_NO_INSTRUMENT_FUNCTION_ENTRY_EXIT properly when
>> not doing -pg or -mfentry (that is, set it to 1).
>
> The only way would be to handle it in build_decl itself.
> There seem to be a
On Thu, Sep 4, 2014 at 10:48 AM, Jan-Benedict Glaw wrote:
> Hi!
>
> -Wlogical-not-parentheses was enabled recently via -Wall, and it
> triggered for rx-elf
> (http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=350506)
> on a build with config-list.mk, where a GCC of the same revision i
On Thu, Sep 4, 2014 at 10:59 AM, Bin Cheng wrote:
> Hi,
> As reported by pr62631, case ivopts-lt-2.c is failed on sparc64. The root
> cause is shiftadd_cost calculated on sparc64 is huge which prevents gcc from
> choosing the wanted candidate. The problem with IVOPT is it always assumes
> that s
Ah, right you are. (Curiously I still can't find Richard's previous message in
Thunderbird!)
for first patch, gcc/testsuite/ChangeLog:
* gcc.target/aarch64/vget_high_1.c: New test.
* gcc.target/aarch64/vget_low_1.c: Likewise.
for second patch, gcc/ChangeLog:
* config/a
On Thu, Sep 4, 2014 at 3:06 PM, Yury Gribov wrote:
> Hi all,
>
> This patch adds a Vim config (.local.vimrc) to root folder. This would allow
> automatic setup of GNU formatting for C/C++/Java/Lex files in GCC (similar
> to what we already have for Emacs via .dir-locals.el). The formatting is
> bo
On 4 September 2014 14:21, Alan Lawrence wrote:
> Ah, right you are. (Curiously I still can't find Richard's previous message
> in Thunderbird!)
>
> for first patch, gcc/testsuite/ChangeLog:
>
> * gcc.target/aarch64/vget_high_1.c: New test.
> * gcc.target/aarch64/vget_low_1.c: Like
On 4 September 2014 06:34, Carrot Wei wrote:
> Changed the coding style.
>
>
> 2014-09-03 Guozhi Wei
>
> PR target/62040
> * gcc.target/aarch64/pr62040.c: New test.
Thank you. OK /Marcus
On 04 Sep 15:08, Thomas Schwinge wrote:
> I'm facing one problem; I guess the crucial detail is that in my scenario
> I'm using the linker plugin. The lto-wrapper is not being executed (and
> thus no mkoffload being run), because »num_claimed_files == 0«.
Yeah I missed that. I tested this patch
Hi!
On Thu, 04 Sep 2014 15:08:06 +0200, I wrote:
> On Tue, 2 Sep 2014 21:49:46 +0400, Ilya Verbin wrote:
> > This patch allows to compile binaries with offloading without passing -flto
> > option, and
> > w/o performing link-time optimizations of the host code.
>
> Thanks for working on this!
>
On Thu, Sep 4, 2014 at 12:07 AM, Bill Schmidt
wrote:
> Hi,
>
> The *vsx_extract__load pattern performs a scalar load of memory
> when possible, rather than a vector load followed by an extract. The
> assembly for the pattern always loads the 0th memory doubleword element,
> but the pattern match
On Thu, Sep 4, 2014 at 12:28 AM, Bill Schmidt
wrote:
> Hi,
>
> This patch adds more special handling to analyze_swaps to allow us to
> improve more computations. Previously I had disallowed VEC_SELECT in
> all cases. This is now changed to allow a select of a single lane,
> either for an extract
Hi,
It's worth setting up the FPCR to flush to zero, round to nearest modes
especially under Ofast and ffast-math.
This patch attempts to do so and additionally cleans up ENDFILE_SPEC for
AArch64 GNU/Linux targets.
Built and tested cross with aarch64-none-elf. A native bootstrap and
test
On Thu, Sep 4, 2014 at 3:06 PM, Jakub Jelinek wrote:
> On Thu, Sep 04, 2014 at 02:57:47PM +0200, Richard Biener wrote:
>> Note that I think we arrived at the point where the loop structure
>> has annotations that are required for correctness :/ (simduid
>> for example - if that goes away we do ..
Hi,
While changing register costs for AArch64 (patches to follow), the test
gcc.target/aarch64/vect-mult.c fails. This is caused by ree inserting a TI mode
copy of a DI
register. Since TI mode requires 2 registers, this results in silent corruption
of the 2nd register.
After split2:
(insn 149
this patch enabled stack shrink-wrap support on AArch64.
no regression on aarch64-none-elf bare-metal.
aarch64 bootstrap OK.
ok to install?
2014-09-04 Renlin Li
gcc/
* config/aarch64/aarch64.md (return): New expand.
(simple_return): Likewise.
* config/aarch64/aarch64.c (aarch64_use_retur
currently, the instruction sink in "prepare_shrink_wrap" is a bit conservative
that some further optimization opportunities have been missed.
given the prologue use register A by:
(store A, [sp + offset])
then given the entry_basic_block contains a simply register copy like:
(move A, B)
c
Hi,
This is a set of patches improving register costs on AArch64. The first fixes
aarch64_register_move_cost() to support CALLER_SAVE_REGS and POINTER_REGS so
costs are calculated
correctly in the register allocator.
ChangeLog:
2014-09-04 Wilco Dijkstra
* gcc/config/aarch64/aarch64.c
This patch fixes a bug in aarch64_register_move_cost(): GET_MODE_SIZE is in
bytes not bits. As a
result the FP2FP cost doesn't need to be set to 4 to catch the special case for
Q register moves.
ChangeLog:
2014-09-04 Wilco Dijkstra
* gcc/config/aarch64/aarch64.c (aarch64_register_mov
Cleanup inconsistent use of __extension__.
ChangeLog:
2014-09-04 Wilco Dijkstra
* gcc/config/aarch64/aarch64.c: Cleanup use of __extension__.
---
gcc/config/aarch64/aarch64.c | 38 +++---
1 file changed, 11 insertions(+), 27 deletions(-)
diff --git a/
This patch adds regmove_costs for Cortex-A57 and A53, and sets the cost of
GP2FP/FP2GP higher than
memory cost to block the register allocator allocating integer values in FP
registers.
Overall these patches give 2-3% speedup on SPEC.
This passes all regression tests (with this fix
https://gcc.
On 2014-09-04 3:37 AM, Tom de Vries wrote:
On 03-09-14 18:58, Tom de Vries wrote:
I've build the patch and ran the fuse-caller-save tests, and I'm
currently
bootstrapping and reg-testing it on x86_64.
Vladimir,
This patch fixes a problem (found on s390) in one of the committed
fuse-caller-sa
On Thu, Sep 4, 2014 at 6:33 AM, Bin Cheng wrote:
> Hi,
> This patch is to fix a potential bug in arm pattern "arm_movqi_insn".
>
> For the pattern,
> (define_insn "*arm_movqi_insn"
> [(set (match_operand:QI 0 "nonimmediate_operand" "=r,r,r,l,r,l,Uu,r,m")
> (match_operand:QI 1 "general_op
On Thu, Sep 4, 2014 at 7:08 AM, Bin Cheng wrote:
> Hi,
> This patch is posted/approved before at
> https://gcc.gnu.org/ml/gcc-patches/2014-07/msg01398.html
> Unfortunately, it was reverted because a latent bug revealed causing glibc
> build failure and I didn't have enough time to fix back at that
On 4 September 2014 15:44, Wilco Dijkstra wrote:
> Hi,
>
> This is a set of patches improving register costs on AArch64. The first fixes
> aarch64_register_move_cost() to support CALLER_SAVE_REGS and POINTER_REGS so
> costs are calculated
> correctly in the register allocator.
>
> ChangeLog:
> 20
On 4 September 2014 15:45, Wilco Dijkstra wrote:
> This patch fixes a bug in aarch64_register_move_cost(): GET_MODE_SIZE is in
> bytes not bits. As a
> result the FP2FP cost doesn't need to be set to 4 to catch the special case
> for Q register moves.
>
> ChangeLog:
> 2014-09-04 Wilco Dijkstra
On 4 September 2014 15:45, Wilco Dijkstra wrote:
> Cleanup inconsistent use of __extension__.
>
> ChangeLog:
> 2014-09-04 Wilco Dijkstra
>
> * gcc/config/aarch64/aarch64.c: Cleanup use of __extension__.
Write a proper ChangeLog entry please.
/Marcus
> From: Marcus Shawcroft [mailto:marcus.shawcr...@gmail.com]
> > - NAMED_PARAM (FP2FP, 4)
> > + NAMED_PARAM (FP2FP, 2)
>
> This is not directly related to the change below and it is missing
> from the ChangeLog. Originally this number had to be > 2 in order
> for secondary reload to kick in.
On 4 September 2014 16:39, Marcus Shawcroft wrote:
> On 4 September 2014 15:45, Wilco Dijkstra wrote:
>> Cleanup inconsistent use of __extension__.
>>
>> ChangeLog:
>> 2014-09-04 Wilco Dijkstra
>>
>> * gcc/config/aarch64/aarch64.c: Cleanup use of __extension__.
>
> Write a proper Chang
Ping!
> -Original Message-
> From: gcc-patches-ow...@gcc.gnu.org [mailto:gcc-patches-ow...@gcc.gnu.org]
> On Behalf Of Matthew Fortune
> Sent: 18 August 2014 14:25
> To: 'gcc-patches@gcc.gnu.org' (gcc-patches@gcc.gnu.org)
> Cc: Richard Sandiford; Eric Christopher (echri...@gmail.com)
> Sub
Ping!
> -Original Message-
> From: gcc-patches-ow...@gcc.gnu.org [mailto:gcc-patches-ow...@gcc.gnu.org]
> On Behalf Of Matthew Fortune
> Sent: 22 August 2014 10:43
> To: 'gcc-patches@gcc.gnu.org' (gcc-patches@gcc.gnu.org); Eric Christopher
> (echri...@gmail.com)
> Cc: Moore, Catherine (cat
On 4 September 2014 16:41, Wilco Dijkstra wrote:
>> From: Marcus Shawcroft [mailto:marcus.shawcr...@gmail.com]
>> > - NAMED_PARAM (FP2FP, 4)
>> > + NAMED_PARAM (FP2FP, 2)
>>
>> This is not directly related to the change below and it is missing
>> from the ChangeLog. Originally this number had
On 4 September 2014 15:47, Wilco Dijkstra wrote:
> This patch adds regmove_costs for Cortex-A57 and A53, and sets the cost of
> GP2FP/FP2GP higher than
> memory cost to block the register allocator allocating integer values in FP
> registers.
>
> Overall these patches give 2-3% speedup on SPEC.
On Sep 4, 2014, at 12:22 , Richard Biener wrote:
> So I tend to think that removing / delaying traps is ok unless you
> can catch them within the active EH scheme.
> Certainly that Oliver excludes loads/stores (but not integer
> division!) points at the fact that preserving the order of
> traps
On Tue, 2 Sep 2014, Richard Sandiford wrote:
> Also, i386 was robust against uses of %& in inline asm. The patch
> makes sure the other ports are too. Using %& in inline asm would
> often be a mistake, but it should at least trigger a proper error
> rather than an ICE.
>
> Tested on x86_64-linux
On 09/04/2014 07:04 AM, Ramana Radhakrishnan wrote:
> gcc/Changelog
>
> 2014-09-04 Marcus Shawcroft
> Ramana Radhakrishnan
>
>* config/aarch64/aarch64-elf-raw.h (ENDFILE_SPEC): Add
> crtfastmath.o.
>* config/aarch64/aarch64-linux.h
> (GNU_USER_TARGET_MATH
On Sep 4, 2014, at 4:14 AM, Ramana Radhakrishnan
wrote:
>> --- a/gcc/testsuite/lib/target-supports.exp
>> +++ b/gcc/testsuite/lib/target-supports.exp
>> @@ -2293,8 +2293,8 @@ proc check_effective_target_arm_little_endian { } {
>> proc check_effective_target_arm_vect_no_misalign { } {
>> retur
On Wed, 3 Sep 2014, Uros Bizjak wrote:
> > So I think the default timeout that's used for really quick tests should
> > be extended a bit. I propose a factor of 2, just not to make it too
> > excessive, at least for the beginning (maybe it'll have to be higher
> > eventually).
>
> Or you can ju
Gerald Pfeifer writes:
> On Tue, 2 Sep 2014, Richard Sandiford wrote:
>> Also, i386 was robust against uses of %& in inline asm. The patch
>> makes sure the other ports are too. Using %& in inline asm would
>> often be a mistake, but it should at least trigger a proper error
>> rather than an IC
On Wed, Sep 3, 2014 at 10:54 AM, Aldy Hernandez wrote:
> [Jason, Richard]: Is it useful for my patches to contain ChangeLog entries?
> I find them mildly annoying for something that will inevitably be rewritten
> multiple times, but if it aids in reviewing my WIP, I am more than happy to
> continu
I think this merge caused bootstrap failure on Linux/i686
https://gcc.gnu.org/ml/gcc-regression/2014-09/msg00010.html
I incorrectly pushed my branch onto trunk. It's being reverted.
Hi James,
Yes we can just mark operand 3 as "&r".
PFB, the updated patch. Ok for trunk?
regards,
Venkat.
gcc/ChangeLog
2014-09-04 Venkataramanan Kumar
* config/aarch64/aarch64.md (stack_protect_test_) Add register
constraint for operand 0 and remove write only constraint from o
On September 4, 2014 7:54:14 PM CEST, Aldy Hernandez wrote:
>
>> I think this merge caused bootstrap failure on Linux/i686
>>
>> https://gcc.gnu.org/ml/gcc-regression/2014-09/msg00010.html
>>
>>
>
>I incorrectly pushed my branch onto trunk. It's being reverted.
Too bad!
;)
Richard.
Hi, FWIW I saw the same problem on arm* and aarch64 targets.
On 4 September 2014 20:34, Aldy Hernandez wrote:
> On 09/04/14 11:23, Richard Biener wrote:
>>
>> On September 4, 2014 7:54:14 PM CEST, Aldy Hernandez
>> wrote:
>>>
>>>
I think this merge caused bootstrap failure on Linux/i686
>
On 03-09-2014 11:01, Maciej W. Rozycki wrote:
> On Tue, 2 Sep 2014, Adhemerval Zanella wrote:
>
>> Ping.
>>
>> On 19-08-2014 13:54, Adhemerval Zanella wrote:
>>> Ping.
>>>
>>> On 06-08-2014 17:21, Adhemerval Zanella wrote:
On 01-08-2014 12:31, Joseph S. Myers wrote:
> On Thu, 31 Jul 2014,
On 09/04/14 11:23, Richard Biener wrote:
On September 4, 2014 7:54:14 PM CEST, Aldy Hernandez wrote:
I think this merge caused bootstrap failure on Linux/i686
https://gcc.gnu.org/ml/gcc-regression/2014-09/msg00010.html
I incorrectly pushed my branch onto trunk. It's being reverted.
To
> On Thu, Sep 4, 2014 at 5:58 AM, Andi Kleen wrote:
> >>
> >> Anyway, removing !optimize checks in favor of flag_no_inline checks
> >> and initializing that properly is a cleanup as well.
> >
> > Patch looks good to me.
>
> Unfortunately it doesn't pass bootstrap (inline-summary re-use
> between
On Thu, 4 Sep 2014, Richard Sandiford wrote:
> Is this stage 1 libgcc or a later libgcc? Seems unlikely if stage 1.
Stage 1. I kicked off a non-parallel build, which just failed as
follows:
/scratch2/tmp/gerald/OBJ-0904-1719/./gcc/xgcc
-B/scratch2/tmp/gerald/OBJ-0904-1719/./gcc/
-B/home/geral
Dunno, if I'm allowed to make calls on what an obvious patch is,
considering I completely broke trunk with my last commit to the
debug-early branch, but I'll take my chances...
Yet another *.def file that needs handling in the TAGS file.
Committed to trunk as obvious.
Aldy
commit be2a57c0df76
Gerald Pfeifer writes:
> On Thu, 4 Sep 2014, Richard Sandiford wrote:
>> Is this stage 1 libgcc or a later libgcc? Seems unlikely if stage 1.
>
> Stage 1. I kicked off a non-parallel build, which just failed as
> follows:
>
> /scratch2/tmp/gerald/OBJ-0904-1719/./gcc/xgcc
> -B/scratch2/tmp/gerald
Matthew Fortune writes:
> Ping!
For the record, I agree this is the right fix.
Thanks,
Richard
>> -Original Message-
>> From: gcc-patches-ow...@gcc.gnu.org [mailto:gcc-patches-ow...@gcc.gnu.org]
>> On Behalf Of Matthew Fortune
>> Sent: 18 August 2014 14:25
>> To: 'gcc-patches@gcc.gnu.or
On Thu, 2014-09-04 11:34:57 -0700, Aldy Hernandez wrote:
> On 09/04/14 11:23, Richard Biener wrote:
> > On September 4, 2014 7:54:14 PM CEST, Aldy Hernandez
> > wrote:
> > > > I think this merge caused bootstrap failure on Linux/i686
> > > > https://gcc.gnu.org/ml/gcc-regression/2014-09/msg00010
On Tue, 2014-09-02 at 19:50 +0200, Andi Kleen wrote:
> > I suspect the bulk of them currently are coming from the safe_as_a
> > calls within NEXT_INSN and PREV_INSN; do you happen to have
> > information handy on that?
>
> Yes that's right:
>
> - 1.03% lto1[.] bool
> is_a
On Thu, Sep 04, 2014 at 03:22:15PM +0200, Richard Biener wrote:
> On Thu, Sep 4, 2014 at 3:06 PM, Yury Gribov wrote:
> > Hi all,
> >
> > This patch adds a Vim config (.local.vimrc) to root folder. This would allow
> > automatic setup of GNU formatting for C/C++/Java/Lex files in GCC (similar
> > t
The attached trivial patch strengthens a param from rtx to rtx_insn *,
and thus falls under the pre-approval granted by Jeff here:
https://gcc.gnu.org/ml/gcc-patches/2014-08/msg01310.html
Bootstrapped on x86_64-unknown-linux-gnu (Fedora 20), and has been
rebuilt as part of a config-list.mk build
On Thu, Sep 04, 2014 at 04:04:17PM -0400, David Malcolm wrote:
> --- a/gcc/rtl.h
> +++ b/gcc/rtl.h
> @@ -195,6 +195,7 @@ union rtunion
>unsigned int rt_uint;
>const char *rt_str;
>rtx rt_rtx;
> + rtx_insn *rt_insn;
>rtvec rt_rtvec;
>enum machine_mode rt_type;
>addr_diff_vec
On Thu, 4 Sep 2014, Alan Modra wrote:
> > In fact if you look at the corresponding location expression for
> > -fno-section-anchors code you get something quite screwy too.
> >
> > 018f 0108 0114 (DW_OP_breg10 (r10): 0; DW_OP_addr: 144;
> > DW_OP_plus; DW_OP_stack_value
> >
> > whic
The attached patch strengthens both params of the generated insn_latency
function from rtx to rtx_insn *, and thus falls under the pre-approval
granted by Jeff here:
https://gcc.gnu.org/ml/gcc-patches/2014-08/msg01310.html
Bootstrapped on x86_64-unknown-linux-gnu (Fedora 20), and has been
rebuil
On Thu, 2014-09-04 at 22:22 +0200, Jakub Jelinek wrote:
> On Thu, Sep 04, 2014 at 04:04:17PM -0400, David Malcolm wrote:
> > --- a/gcc/rtl.h
> > +++ b/gcc/rtl.h
> > @@ -195,6 +195,7 @@ union rtunion
> >unsigned int rt_uint;
> >const char *rt_str;
> >rtx rt_rtx;
> > + rtx_insn *rt_insn;
The conditions for inhibit_libc to activate (i.e. for library
headers to be absent) are IMO a bit too automatic and the effect
is too subtle and serious in some situations. For example, if
you pre-install target headers in $target_header_dir, gcc will
find them and use them, but still inhibit_libc
The directory at $target_header_dir is already inspected in
gcc/configure, for e.g. glibc version and stack protector
support, but not for setting inhibit_libc. This is just
inconsistent and the obvious resolution to me is to inhibit
inhibit_libc when a target *does* "have its own set of headers",
This adds an option to allow programs and libraries built
*without* inhibit_libc to stay compatible with system libraries
(really: libgcc_s.so.1) built *with* inhibit_libc, at the cost
of the registration. As mentioned, that's a one-way
compatibility barrier.
While it's nice to avoid the overhead
My extend* pattern patches exposed a problem elsewhere. I don't build
java so I didn't see it. This fixes it. Also handles the zero-extend
case, that had the same problem. Pre-approved by David, committed.
Segher
2014-09-04 Segher Boessenkool
PR target/63165
* config/rs6
The patch below removes a sh*-*-* specific dg-options line
from gcc.c-torture/execute/pr44683.c. That line is
unnecessary because now -mieee is a default option on sh*.
I've applied it as an obvious change specific to sh.
Tested on i686-linux and sh-linux.
BTW, Jeff's comment on pr39228.c makes m
On Sep 4, 2014, at 5:22 PM, Kaz Kojima wrote:
> BTW, Jeff's comment on pr39228.c makes me think that this test
> can be moved into execute/ieee. Thought?
I don’t see a down side, specially if we know that the test case is picky about
ieee.
Hi,
when opening a file with a name containing an ASCII null character,
the name is truncated at the first null since the IO API's take
null-terminated C strings. By storing such a C string in gfc_unit
instead of the original Fortran string INQUIRE for the file name will
return the correct name, a
The attached trivial patch strengthens a return type from rtx to
rtx_insn *,
and thus falls under the pre-approval granted by Jeff here:
https://gcc.gnu.org/ml/gcc-patches/2014-08/msg01310.html
Bootstrapped on x86_64-unknown-linux-gnu (Fedora 20), and has been
rebuilt as part of a config-list.mk
It is desirable for various reasons to stop target libraries from
using host-side tm.h: making the headers work on both host and target
(and on build as well) is fragile (especially when dealing with macros
depending on command-line options, which need different definitions
when being used for the
The attached patch strengthens both params of fixup_args_size_notes from
rtx to rtx_insn * (eliminating a checked cast), and thus falls under the
pre-approval granted by Jeff here:
https://gcc.gnu.org/ml/gcc-patches/2014-08/msg01310.html
Bootstrapped on x86_64-unknown-linux-gnu (Fedora 20), and
I've attached the revised patch. Bootstrapped and no test regressions
on x86_64/linux with 4.9 branch. Ok for 4.9 branch? While the bug
doesn't show up in trunk, seems obvious that this should go to trunk
as well. Is it ok for trunk if tests pass?
Btw, is g++.dg/opt the right directory for the tes
The attached patch strengthens the 2nd and 3rd params of
modified_between_p from const_rtx to const rtx_insn * (eliminating a
checked cast), and thus falls under the pre-approval granted by Jeff
here:
https://gcc.gnu.org/ml/gcc-patches/2014-08/msg01310.html
Bootstrapped on x86_64-unknown-linux-g
On Thu, Sep 04, 2014 at 10:05:38PM +0100, Maciej W. Rozycki wrote:
> On Thu, 4 Sep 2014, Alan Modra wrote:
>
> > > In fact if you look at the corresponding location expression for
> > > -fno-section-anchors code you get something quite screwy too.
> > >
> > > 018f 0108 0114 (DW_OP_bre
>> Here is an attempt to do the value range computation in promoted_mode's
>> type when it is overflowing. Bootstrapped on x86-84.
>
> Err - I think you misunderstood this as a suggestion to do this ;)
> value-ranges should be computed according to the type not according
> to the (promoted) mode.
The attached trivial patch strengthens a local variable in cse.c from
rtx to rtx_insn *, allowing the elimination of a checked cast, and thus
falls under the pre-approval granted by Jeff here:
https://gcc.gnu.org/ml/gcc-patches/2014-08/msg01310.html
Bootstrapped on x86_64-unknown-linux-gnu (Fedo
gcc/
* jump.c (delete_related_insns): Introduce a new local "table" by
replacing JUMP_TABLE_DATA_P with a dyn_cast, then use the
get_labels method of "table" to simplify access to the labels in
the jump table.
---
gcc/jump.c | 12 ++--
1 file changed, 6 inse
1 - 100 of 136 matches
Mail list logo
