e.exp -v -v
>> --target_board=microblaze-xilinx-gdb"
>> This will run only the gcc.c-torture/execute/execute.exp tests.
>>
>>>gcc result:
>>>
>>> === gcc Summary ===
>>>
>>> # of expected passes 48
On Sat, Sep 20, 2014 at 10:42:01PM -0400, Jason Merrill wrote:
> On 09/18/2014 10:12 AM, Jakub Jelinek wrote:
> >Clobber stmts, being artificial statements, were certainly never
> >meant to be instrumented. In 4.8 when asan has been introduced into gcc,
> >the lhs of clobber could be only a decl a
On 09/18/2014 10:12 AM, Jakub Jelinek wrote:
Clobber stmts, being artificial statements, were certainly never
meant to be instrumented. In 4.8 when asan has been introduced into gcc,
the lhs of clobber could be only a decl and as a whole decl store would not
be really instrumented, but with *thi
Some subtests were reported as UNSUPPORTED when running under LTO.
That was just because the relevant variables were optimized out.
Mark those variables as used. Now const-volatile reports 192 PASS.
gcc/testsuite/ChangeLog
* gcc.dg/guality/const-volatile.c (i): Mark as used.
(ci):
On Sat, Sep 20, 2014 at 3:04 AM, Anthony Green wrote:
>
>> Attached patch fixes libgo reflect test failure with libffi closures.
>> The gccgo compiler started to use FFI closures recently; the compiler
>> passes ffi_type_void for structures with zero members.
>
> Why not just pass an FFI_TYPE_STRU
When adding DW_TAG_restrict_type I made a mistake when updating the
code that handled types with multiple modifiers. This patch fixes it
by putting the logic for finding the "sub-qualified" type in a separate
function and fall back to adding the modifiers separately if there is
no such existing typ
Old GDB might show short and long as short int and long int. This made
gcc.dg/guality/const-volatile.c ans restrict.c fail on older GDBs.
According to the patch that changed this in newer versions of GDB
this was a bug: https://sourceware.org/ml/gdb-patches/2012-09/msg00455.html
The patch transfo
I committed this libgo patch to mainline to restore a copyright notice
that was accidentally removed.
Ian
diff -r 408e2e4289f9 libgo/runtime/mgc0.c
--- a/libgo/runtime/mgc0.c Fri Sep 19 11:53:15 2014 -0700
+++ b/libgo/runtime/mgc0.c Sat Sep 20 13:41:17 2014 -0700
@@ -1,4 +1,4 @@
-
+// Copyright 2
Hi!
On Thu, 2014-09-18 11:19:21 +0100, James Greenhalgh
wrote:
> As discussed in https://gcc.gnu.org/ml/gcc-patches/2014-09/msg01334.html
> The construct
>
> (clobber (match_scratch 0 "r"))
>
> is invalid - operand 0 must be marked either write or read/write.
>
> Likewise
>
> (match_* 0
The instruction patterns are now called subf, with the corresponding
operand order, to be less confusing. I tried using the "sub" extended
mnemonics instead but that only made things way, way worse.
Do not allow an integer as second operand of sub3; expand doesn't
use it. Only strlensi used it,
Also change type "compare" to "two" for the dot forms.
2014-09-20 Segher Boessenkool
* config/rs6000/rs6000.md (div3): Fix comment. Use a different
insn for divides by integer powers of two.
(div3_sra, *div3_sra_dot, *div3_sra_dot2): New.
(mod3): Fix formattin
2014-09-20 Segher Boessenkool
* config/rs6000/rs6000.md (ashr3, *ashr3, *ashrsi3_64,
*ashr3_dot, *ashr3_dot2): Clobber CA_REGNO.
(floatdisf2_internal2): Ditto.
(ashrdi3_no_power): Ditto. Fix formatting.
---
gcc/config/rs6000/rs6000.md | 44 ++
Use a new code iterator to handle IOR, XOR. Also, we can now fold
the AND patterns together with the boolean_or_operator patterns.
2014-09-20 Segher Boessenkool
* config/rs6000/rs6000.md (iorxor): New code_iterator.
(iorxor): New code_attr.
(IORXOR): New code_attr.
2014-09-20 Segher Boessenkool
* config/rs6000/rs6000.md (ctz2, ffs2, popcount2,
popcntb2, popcntd2, parity2, parity2_cmpb):
Tidy.
---
gcc/config/rs6000/rs6000.md | 70 ++---
1 file changed, 35 insertions(+), 35 deletions(-)
di
>
> Yep, tree_to_shwi will check it. The old code did generic expression folding
> and
> called tree_to_shwi on result, so the only difference is that old code will
> accept
> unfolded expressions that miraculously folds into constant. I think it is
> bug to
> have those in IL especially on p
On Sep 20, 2014, at 3:04 AM, Anthony Green wrote:
>
> Why not just pass an FFI_TYPE_STRUCT with zero members?
My information may be old or irrelevant but I have used structs with no members
with gcc backend, but with nonzero size and alignment, and ran into backend
problems, particularly on
2014-09-20 Segher Boessenkool
* config/rs6000/rs6000.md (*neg2_internal): Delete.
(two anonymous define_insn and two define_split): Delete.
(*neg2, *neg2_dot, *neg2_dot2): New.
---
gcc/config/rs6000/rs6000.md | 65 +++--
1 file
Just the usual tidying. Also use the "not" extended mnemonic instead
of the "nor" that translates to.
2014-09-20 Segher Boessenkool
* config/rs6000/rs6000.md (*one_cmpl2): Generate "not" insn.
(two anonymous define_insn and two define_split): Delete.
(*one_cmpl2_dot,
Currently NE isn't handled at all. Handle it the same as EQ, LTU, GTU.
2014-09-20 Segher Boessenkool
* config/rs6000/rs6000.c (rs6000_rtx_costs) : New.
---
gcc/config/rs6000/rs6000.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/gcc/config/rs6000/rs6000.c b/gcc/config/rs6000
This series handles most of the "small" changes for handling the carry
bit; it does not touch the "add" and scc patterns yet, and no pattern
sets or uses the carry yet either (only clobbers).
Tested as usual, no regressions. Are these okay to apply?
Segher
- - -
Make the carry bit non-alloc
Hi FX,
I missed that op points still on the memory here. So corrected patch
is inlined below.
Kai
Index: predicates.md
===
--- predicates.md (Revision 215364)
+++ predicates.md (Arbeitskopie)
@@ -73,9 +73,18 @@
;; Ret
mmary ===
>>
>> # of expected passes 48408
>> # of unexpected failures 17253
>> # of unexpected successes 1
>> # of expected failures97
>> # of unresolved testcases 16570
>> # of unsupported tests
AFAICT the lines 11200-11222 in gcc/fortran/resolve.c are a copy of
the lines 11176-11198. The following patch removes the duplicated
lines. OK for the trunk?
Dominique
--- ../_clean/gcc/fortran/resolve.c 2014-09-20 13:56:57.0 +0200
+++ gcc/fortran/resolve.c 2014-09-20 14:01:42
Hi,
this patch makes ipa_polymorphic_call_context construction to be useful for
forward propagation passes (such as ipa-devirt). My original implementation
takes polymorphic call statment as a parameter and walks backward the SSA
graph.
Now one can construct the polymorphic call info for any cons
> The patch you sent (copied below) does not fix the darwin regression. It
> still fails with the same ICE on attached valid code (in 64-bit mode; it
> compiles with -m32).
The proposed patch by Iain’s patch
(https://gcc.gnu.org/ml/gcc-patches/2014-09/msg01141.html and attached), which
Mike se
97
# of unresolved testcases 16570
# of unsupported tests1854
/upstream/build-gcc/gcc/xgcc version 5.0.0 20140920 (experimental) (GCC)
Look at gcc.sum and gcc.log to find out what is causing the large number of
unexpected failures. A large number of unresolved test ca
Hi Kai,
The patch you sent (copied below) does not fix the darwin regression. It still
fails with the same ICE on attached valid code (in 64-bit mode; it compiles
with -m32).
FX
a.C
Description: Binary data
> Index: config/i386/predicates.md
> ==
> On 09/19/14 22:04, Jan Hubicka wrote:
> >Hi,
> >int_bit_position is used by ipa-devirt's type walking code. It is currently
> >a bottleneck
> >since I introduced speculation into contextes (I plan to solve this by
> >changing the
> >way i cache results). But this patch seems to make sense anyw
ted failures 17253
# of unexpected successes 1
# of expected failures97
# of unresolved testcases 16570
# of unsupported tests1854
/upstream/build-gcc/gcc/xgcc version 5.0.0 20140920 (experimental) (GCC)
make[2]: Leaving directory `/upstr
Hi Tobias,
> However, I wanted to point out that seemingly trivial and obviously
> correct patches can have a downside. (One can still do such changes, but
> at least one should have weighted them against the downside.)
I agree, that's why I asked explicitly.
Joost
On 09/19/14 22:04, Jan Hubicka wrote:
Hi,
int_bit_position is used by ipa-devirt's type walking code. It is currently a
bottleneck
since I introduced speculation into contextes (I plan to solve this by changing
the
way i cache results). But this patch seems to make sense anyway: we do not need
Hi Joost and Thomas,
On 20.09.2014 12:02, Thomas Koenig wrote:
A somewhat trivial patch to cleanup whitespace issues in comments: sed "s/\. \*\//\.
\*\//g"
Tested with a recompile only. Ok for trunk ?
OK. (Obvious, really).
I want to point a downside of massive code changes: It makes it mo
Hi Alessandro et al.,
I have now committed (Rev. 215421) the attached patch, which includes a
test case for it.
Thanks for the report and the patch Alessandro!
Tobias
On 15.09.2014 23:29, Tobias Burnus wrote:
On 15.09.2014 22:23, Alessandro Fanfarillo wrote:
In attachment a test case which
This patch adds a CO_BROADCAST and prepares a bit for CO_REDUCE.
Both functions permit arguments with allocatable components
(nonpolymophic or polymorphic), CO_BROADCAST also permits polymorphic
arguments. This patch doesn't support allocatable/polymorphic arguments
but otherwise CO_BROADCAST
On Fri, 2014-09-19 22:26:59 +0200, Jan-Benedict Glaw wrote:
> On Thu, 2014-09-18 16:55:35 -0500, Joel Sherrill
> wrote:
> > I only see one RTEMS target that has been built in the top page.
> > Are more than the powerpc-rtems being built? How can I check?
>
> The builders work down their list, a
[replying to an ancient post here..]
Uros Bizjak writes:
> Hello!
>
> Attached patch fixes libgo reflect test failure with libffi closures.
> The gccgo compiler started to use FFI closures recently; the compiler
> passes ffi_type_void for structures with zero members.
Why not just pass an FFI_
Hi Joost,
> A somewhat trivial patch to cleanup whitespace issues in comments: sed "s/\.
> \*\//\. \*\//g"
>
> Tested with a recompile only.
>
> Ok for trunk ?
OK. (Obvious, really).
Thomas
A somewhat trivial patch to cleanup whitespace issues in comments: sed "s/\.
\*\//\. \*\//g"
Tested with a recompile only.
Ok for trunk ?
gcc/fortran/ChangeLog:
2014-09-20 Joost VandeVondele
* trans-expr.c (gfc_reset_vptr): Fix comment whitespace.
(gfc_conv_class_to_cl
Tested on ia64-suse-linux and checked in as obvious.
Andreas.
* config/ia64/ia64.md: Remove constraints from define_split
patterns.
diff --git a/gcc/config/ia64/ia64.md b/gcc/config/ia64/ia64.md
index 986ef02..572870f 100644
--- a/gcc/config/ia64/ia64.md
+++ b/gcc/config/ia64/ia6
39 matches
Mail list logo
