Hi,
this patch adds computation and streaming of mangled type names. As suggested
by Jason,
it simple calls DECL_ASSEMBLER_NAME on all names types and lets C++ supply them.
This makes it possible to stablish precise ODR type equivalency at LTO (till
now we can
do that only for complete class typ
On Wed, Sep 10, 2014 at 11:23:34PM +0200, Jakub Jelinek wrote:
> On Wed, Sep 10, 2014 at 11:08:22PM +0200, Jakub Jelinek wrote:
> > Perhaps better approach might be if we have some way how to synchronize
> > among
> > multiple expect processes and spawn only as many expects (of course, per
> > che
Ping?
> -Original Message-
> From: gcc-patches-ow...@gcc.gnu.org [mailto:gcc-patches-
> ow...@gcc.gnu.org] On Behalf Of Thomas Preud'homme
> Sent: Wednesday, August 20, 2014 9:28 AM
> To: gcc-patches@gcc.gnu.org
> Subject: [PATCH][ARM] Fix -fcall-saved-rX for X > 7
>
> This patch makes -fc
On Thu, Sep 11, 2014 at 09:51:23AM +0200, Jakub Jelinek wrote:
> I can't find how to query the -jN value passed to make check by the user
> though, both $(MFLAGS) and $(MAKEFLAGS) only contain something like
> --jobserver-fds=3,5 -j from which it is not possible to find out how many
> goals would b
On Thu, 11 Sep 2014, Jan Hubicka wrote:
> Hi,
> this patch adds computation and streaming of mangled type names. As
> suggested by Jason,
> it simple calls DECL_ASSEMBLER_NAME on all names types and lets C++ supply
> them.
> This makes it possible to stablish precise ODR type equivalency at LTO
Hi,
There are a set of SIMD shift intrinsics that have very tight predicates
on the range of immediates they can accept, but have been written with very
loose predicates, bailing out with an error in final if there has been an
issue.
This is a problem if some pass figures out that a value passed
On Wed, Sep 10, 2014 at 7:40 PM, Uros Bizjak wrote:
>> Patch in the bottom extends gather instructions support.
>>
>> Bootstrapped.
>> AVX-512* tests on top of patch-set all pass
>> under simulator.
>>
>> Is it ok for trunk?
>>
>> gcc/
>> * config/i386/sse.md
>> (define_expand "_g
The following adds dumping what patterns get applied with -details.
This is useful for tracking down which patterns cause a miscompile.
Applied.
Richard.
2014-09-11 Richard Biener
* genmatch.c (output_line_directive): Add variant for dump files.
(dt_simplify::gen): Write to
> could it be that the pattern in normal1 should have been '[ab]*/ de*/
> [ep]*/*' ?
I've checked that this fixes the bug in the current trunk split. I.e. files are
stil tested, but now only once. Consider this change added to the previously
submitted patch.
On Thu, Sep 11, 2014 at 2:37 AM, David Malcolm wrote:
> The following patch adds a macro:
>
> /* Get the label that a LABEL_REF references. */
> #define LABEL_REF_LABEL(LABREF) XCEXP (LABREF, 0, LABEL_REF)
>
> and uses it in place of XEXP (foo, 0) for "foo" known to be a
> LABEL_REF, througho
On Wed, Sep 10, 2014 at 10:09 AM, Yury Gribov wrote:
> Hi all,
>
> This is a second version of patch which adds a Vim config (.local.vimrc)
> to root folder to allow automatic setup of GNU formatting for C/C++/Java/Lex
> GCC files.
>
> I've updated the code with comments from Richard and Bernhard
These are copy&paste errors (except the l3 instead of 13 which is just
odd) and they show up on nvptx as type mismatches in the assembly
because of the implicit declaration. Two of the tests had ^M characters
which I also removed.
Tested on x86_64-linux and committed as obvious.
Bernd
commit
> On Sep 10, 2014, at 9:47 PM, Yury Gribov wrote:
>
> Segher Boessenkool kernel.crashing.org> writes:
>> I am saying it is very anti-social to make
>> people's editor behave differently from what they are used to.
>> ...
>> The Emacs dir-locals file simply
>> configures some settings for files
On Thu, Sep 11, 2014 at 11:06 AM, Richard Biener
wrote:
> On Wed, Sep 10, 2014 at 10:09 AM, Yury Gribov wrote:
>> Hi all,
>>
>> This is a second version of patch which adds a Vim config (.local.vimrc)
>> to root folder to allow automatic setup of GNU formatting for C/C++/Java/Lex
>> GCC files.
>>
On 09/11/2014 01:14 PM, pins...@gmail.com wrote:
I don't like auto formatting in any editor.
Ok, so +1 for moving to contrib/.
And some folks already have to deal with two more formatting styles already:
Linux kernel and gnu. So if you add auto formatting to one,
some folks are going to get c
On 09/11/2014 01:18 PM, Richard Biener wrote:
On Thu, Sep 11, 2014 at 11:06 AM, Richard Biener
wrote:
>On Wed, Sep 10, 2014 at 10:09 AM, Yury Gribov wrote:
>>Hi all,
>>
>>This is a second version of patch which adds a Vim config (.local.vimrc)
>>to root folder to allow automatic setup of GNU
I'm getting ready to submit the ptx port and the various changes that
are necessary for it. To start with, here are some patches to deal with
address space issues.
ptx has the concept of an implicit address space: everything (objects on
the stack as well as constant data and global variables)
This is a bug in SRA which replaces a memory reference without taking
care to use the correct address space.
Bootstrapped and tested together with the other patches on x86_64-linux.
Ok?
Bernd
commit 6b9be6e3081c313c024aeabe2d70bc0f8146b429
Author: Bernd Schmidt
Date: Wed Sep 10 16:32:56
The vectorizer can also replace a memory reference without ensuring it
uses the correct address space.
Bootstrapped and tested together with the other patches on x86_64-linux.
Ok?
Bernd
commit e85dbde1aa3396b5e202aa736f96b232a6e11e86
Author: Bernd Schmidt
Date: Wed Sep 10 16:33:40 2014 +
This one isn't a wrong-code issue, just a missed optimization. The
strlen optimizations need to be made to look through
ADDR_SPACE_CONVERT_EXPR to work on ptx.
Bootstrapped and tested together with the other patches on x86_64-linux.
Ok?
Bernd
commit 35d765aeba4ea7d0ba829b2b502c8c7af0c2472
This shows up as failures of gfortran.dg/bessel_[67].f90 on ptx.
According to the man page, the correct declarations are
double jn(int n, double x);
double yn(int n, double x);
and our calls match this, but the argument types are switched in the
decls built by the Fortran frontend. On ptx, suc
Changing the fntype[2] looks wrong to me, as it is also used for powi(double,
int) , where the argument order matches the current version:
> gfc_define_builtin ("__builtin_powi", mfunc_double[2],
> BUILT_IN_POWI, "powi", ATTR_CONST_NOTHROW_LEAF_LIST);
(I don’t see any oth
Fix a mistake in the declaration.
The trunk patch also fixes a few warnings that show up with
-Wsystem-headers.
Tested x86_64-linux, committed to trunk and the 4.9 branch.
commit 4f02e789f77c1d72a75fad0206dbde7728f41c23
Author: Jonathan Wakely
Date: Thu Sep 11 10:38:49 2014 +0100
PR
So I managed to re-introduce PR41043 by implementing the
fold_unary (T1)(X * Y) -> (T1)X * (T1)Y pattern on GIMPLE.
That is because it re-applies recursively on a large
multiplication tree and because if there are multiple uses
of SSA names doing that will expand (aka un-CSE) the
multiplication tr
The following patch completes transitioning
tree-ssa-forwprop.c:associate_* to patterns.
Bootstrapped and tested on x86_64-unknown-linux-gnu.
Richard.
2014-09-11 Richard Biener
* match-plusminus.pd: Complete associate_plusminus patterns.
Properly guard all patterns. Add as
On 11 September 2014 07:22, VandeVondele Joost wrote:
> Jakub,
>
>> First of all, the -j2 testing shows more tests tested in gcc and libstdc++:
>>
>>-# of expected passes 10133
>>+# of expected passes 10152
>>
>>+PASS: 23_containers/set/modifiers/erase/abi_tag.cc (test for exce
Hello,
I would like to start merging offloading-related patches from gomp-4_0-branch
to trunk.
This is the first patch (from r202620), which adds a splay tree and memory
mapping to libgomp.
I removed temporarily device 257 from it. Bootstrapped and regtested on
x86_64-linux.
2014-09-11 Jakub
On Thu, Sep 11, 2014 at 12:11 PM, Bernd Schmidt wrote:
> I'm getting ready to submit the ptx port and the various changes that are
> necessary for it. To start with, here are some patches to deal with address
> space issues.
>
> ptx has the concept of an implicit address space: everything (objects
On Thu, Sep 11, 2014 at 12:12 PM, Bernd Schmidt wrote:
> This is a bug in SRA which replaces a memory reference without taking care
> to use the correct address space.
>
> Bootstrapped and tested together with the other patches on x86_64-linux.
> Ok?
Ok (with adjustments necessary for renaming ap
On Thu, Sep 11, 2014 at 03:28:02PM +0400, Ilya Verbin wrote:
> I would like to start merging offloading-related patches from gomp-4_0-branch
> to trunk.
> This is the first patch (from r202620), which adds a splay tree and memory
> mapping to libgomp.
> I removed temporarily device 257 from it.
On Thu, Sep 11, 2014 at 12:12 PM, Bernd Schmidt wrote:
> The vectorizer can also replace a memory reference without ensuring it uses
> the correct address space.
>
> Bootstrapped and tested together with the other patches on x86_64-linux.
> Ok?
Seeing this it would be nice to abstract away the ex
On Thu, 11 Sep 2014, Richard Biener wrote:
+ /* We can't reassociate floating-point or fixed-point plus or minus
+because of saturation to +-Inf. */
+ (if (!FLOAT_TYPE_P (type) && !FIXED_POINT_TYPE_P (type))
Do you remember if there was a particular reason not to add
|| flag_associative
On Thu, Sep 11, 2014 at 12:12 PM, Bernd Schmidt wrote:
> This one isn't a wrong-code issue, just a missed optimization. The strlen
> optimizations need to be made to look through ADDR_SPACE_CONVERT_EXPR to
> work on ptx.
>
> Bootstrapped and tested together with the other patches on x86_64-linux.
On Thu, 11 Sep 2014, Marc Glisse wrote:
> On Thu, 11 Sep 2014, Richard Biener wrote:
>
> > + /* We can't reassociate floating-point or fixed-point plus or minus
> > +because of saturation to +-Inf. */
> > + (if (!FLOAT_TYPE_P (type) && !FIXED_POINT_TYPE_P (type))
>
> Do you remember if ther
More closely match-up to tree-ssa-forwprop.c code.
Committed.
Richard.
2014-09-11 Richard Biener
* match-plusminus.pd: More closely match tree-ssa-forwprop.c code.
Index: gcc/match-plusminus.pd
===
--- gcc/match-plusmi
Hi,
I'd been putting this patch off in the hope that I might find
time to move these intrinsics to a C/builtin implementation, but it
is probably better to get them right for now and come back to improving
them later.
All four of these suffer the same problem, their "lane" argument should
be a 6
On 11 Sep 13:34, Jakub Jelinek wrote:
> I think it is not useful to split patches on in which sequence they were
> added to the tree. I'd prefer patches for functional parts for the
> differences between trunk and corresponding offloading branch.
> So, one patch should be all the libgomp changes e
Applied.
Richard.
2014-09-11 Richard Biener
* match-plusminus.pd: Fix typo.
* match-conversions.pd: Add pattern for
simplify_conversion_from_bitmask.
Index: gcc/match-conversions.pd
===
--- gcc/match-con
/* ~A + 1 -> -A */
(simplify
(plus (bit_not @0) integer_onep@1)
(if (TREE_CODE (TREE_TYPE (@1)) != COMPLEX_TYPE
|| (TREE_CODE (@1) == COMPLEX_CST
&& integer_onep (TREE_REALPART (@1))
&& integer_onep (TREE_IMAGPART (@1
(negate @0)))
the complex par
On Thu, 11 Sep 2014, Marc Glisse wrote:
> /* ~A + 1 -> -A */
> (simplify
>(plus (bit_not @0) integer_onep@1)
>(if (TREE_CODE (TREE_TYPE (@1)) != COMPLEX_TYPE
> || (TREE_CODE (@1) == COMPLEX_CST
> && integer_onep (TREE_REALPART (@1))
> && integer_onep (TR
Hi all
we have merged the gcc-4_9-branch into linaro/gcc-4_9-branch up to
revision 214896 as r215060. We have also backported this set of revisions:
r211717 as r214313 : [AArch32] TARGET_ATOMIC_ASSIGN_EXPAND_FENV hook
r212927 as r214314 : [AArch32] Enable arm target in
ira-shrinkwrap-prep* testc
Hello,
Patch in the bottom extends integer max/min patterns.
Also, it seems, like rounding variant was generated
for maxmin patterns. Bug fixed.
Bootstrapped.
AVX-512* tests on top of patch-set all pass
under simulator.
Is it ok for trunk?
gcc/
* config/i386/sse.md (VI128_256): Delete.
Hello,
Patch in the bottom extends patterns for rotate, ternlog and align.
Bootstrapped.
AVX-512* tests on top of patch-set all pass
under simulator.
Is it ok for trunk?
gcc/
* config/i386/sse.md
(define_mode_iterator VI48_AVX512VL): New.
(define_expand "_vternlog_maskz")
There's some code in get_uncond_jump_length to emit and then delete a
label and a jump. On ptx we skip register allocation and reload, and
this fails a "reload_completed || bb != NULL" assert in df_insn_delete.
Fixed by instead emitting the two insns into a sequence which we then
just discard.
The nvptx backend is somewhat unusual in that call insns set a pseudo.
The combiner is surprised by this and allows combining them into other
insns, which remain as INSN rather than CALL_INSN. Aborts ensue.
Bootstrapped and tested on x86_64-linux, together with the other
patches. Ok?
Bernd
nvptx will be the first port to use BImode and have
STORE_FLAG_VALUE==-1. That has exposed a bug in combine where we can end
up calling num_sign_bit_copies for a BImode value. However, the return
value is always 1 in that case, so it doesn't tell us anything and is
going to be misinterpreted by
It turns out that we're calling eliminate_regs for global variables
which can't possibly have eliminable regs in their decl. At that point,
reg_eliminate can be NULL. This patch avoids unnecessary work, and
allows us to add an assert to eliminate_regs later.
Bootstrapped and tested on x86_64-l
Hi Jiong,
On 9 September 2014 12:59, Ramana Radhakrishnan
wrote:
> On Mon, Aug 18, 2014 at 11:31 AM, Jiong Wang wrote:
>> this patch enable auto-vectorization for copysignf by using vector
>> bit selection instruction on arm32 when neon available.
>>
I've noticed that your new testcase fails (t
This testcase was breaking because multiple substitutions of ContainerEndA> into T... would lose the original arguments when we pull
the pattern out of the intermediate expansion. So the added assert
guards against that happening again, and we avoid the situation by
simplifying the handling of
On 9 September 2014 12:19, Marcus Shawcroft wrote:
> On 8 September 2014 11:35, Alan Lawrence wrote:
>> This adds a test of all the variants of vld2, vld2q, vld3, vld3q, vld4, and
>> vld4q. These all use typexNxM structs and the OI/CI/XImode mechanism, so the
>> test cross-checks this against pla
On 11/09/14 14:43, Christophe Lyon wrote:
Hi Jiong,
On 9 September 2014 12:59, Ramana Radhakrishnan
wrote:
On Mon, Aug 18, 2014 at 11:31 AM, Jiong Wang wrote:
this patch enable auto-vectorization for copysignf by using vector
bit selection instruction on arm32 when neon available.
I've no
Yes, I had seen that, and the failure is expected. AFAICT the test is correct;
but the implementation of vld[234] is incorrect on bigendian, because of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59810 .
HTH, Alan.
Christophe Lyon wrote:
On 9 September 2014 12:19, Marcus Shawcroft wrote:
Original patch applied cleanly to 4.9 HEAD as r215175.
Marcus Shawcroft wrote:
On 20 August 2014 10:25, Alan Lawrence wrote:
The SIMD-register variant is miscategorized as "alu_reg" despite not using
any ALU registers, and should be "neon_add" for e.g. scheduling.
Tested with check-gcc and ch
On 11 September 2014 13:15, James Greenhalgh wrote:
>
> Hi,
>
> I'd been putting this patch off in the hope that I might find
> time to move these intrinsics to a C/builtin implementation, but it
> is probably better to get them right for now and come back to improving
> them later.
>
> All four o
>> could it be that the pattern in normal1 should have been '[ab]*/ de*/
>> [ep]*/*' ?
>
>Yes, we are running these tests multiple times:
>
>PASS: 23_containers/map/modifiers/erase/abi_tag.cc (test for excess errors)
>PASS: 23_containers/multimap/modifiers/erase/abi_tag.cc (test for excess
>erro
On 11 September 2014 15:45, VandeVondele Joost
wrote:
>
>>> could it be that the pattern in normal1 should have been '[ab]*/ de*/
>>> [ep]*/*' ?
>>
>>Yes, we are running these tests multiple times:
>>
>>PASS: 23_containers/map/modifiers/erase/abi_tag.cc (test for excess errors)
>>PASS: 23_contai
On Thu, Sep 11, 2014 at 10:06:40AM +0200, Jakub Jelinek wrote:
> There is an option to touch say *-parallel/finished file once any of the
> check-parallel-gcc-{1,2,...} goals is done (because when it finishes, it
> means all the tests for the particular check-$lang that are parallelizable
> have ei
Do we need a documentation update?
Jason
Ha OK, I had misunderstood your first email, and thought you had the
test also pass in big endian.
Thanks for the clarification.
On 11 September 2014 15:56, Alan Lawrence wrote:
> Yes, I had seen that, and the failure is expected. AFAICT the test is
> correct; but the implementation of vld[234]
On Thu, Sep 11, 2014 at 03:26:49PM +0100, Marcus Shawcroft wrote:
> On 11 September 2014 13:15, James Greenhalgh wrote:
> >
> > Hi,
> >
> > I'd been putting this patch off in the hope that I might find
> > time to move these intrinsics to a C/builtin implementation, but it
> > is probably better t
Patch attached for commit as I don't have write access.
> -Original Message-
> From: Marcus Shawcroft [mailto:marcus.shawcr...@gmail.com]
> Sent: 04 September 2014 16:23
> To: Wilco Dijkstra
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH 1/4] AArch64: Fix register_move_cost
>
> On 4
Patch attached for commit as I don't have write access.
ChangeLog:
2014-09-11 Wilco Dijkstra
* gcc/config/aarch64/aarch64.c (aarch64_register_move_cost):
Fix Q register move handling. (generic_regmove_cost): Undo raised
FP2FP move cost as Q register moves are now hand
OK, I'll skip this patch for now as HAVE_DESIGNATED_INITIALIZERS should
always be false, so there is no point in cleaning it up.
> -Original Message-
> From: Marcus Shawcroft [mailto:marcus.shawcr...@gmail.com]
> Sent: 04 September 2014 16:42
> To: Wilco Dijkstra
> Cc: gcc-patches@gcc.gnu.
I've kept the integer move costs at 1 - patch attached for commit as I don't
have write access.
ChangeLog:
2014-09-11 Wilco Dijkstra
* gcc/config/aarch64/aarch64.c:
(cortexa57_regmove_cost): New cost table for A57.
(cortexa53_regmove_cost): New cost table for A53.
Gerald Pfeifer writes:
> Hi Igor,
>
> On Wed, 10 Sep 2014, Zamyatin, Igor wrote:
>> + Complete support for http://cilk.org";>Cilk Plus
>> features was added to GCC
>> + [2014-09-02]
features *were* added, plural.
>> + Contributed by Jakub Jelinek, Iyer Balaji and Igor
>> Zamyatin.
Wh
Jan Hubicka writes:
> Hi,
> Libreoffice fails to build because ltrans tries to fetch in variable
> constructor
> that is not shipped there. Fixed thus.
>
> Bootstrapped/regtested x86_64-linux.
>
> Honza
>
> * varpool.c (varpool_node::ctor_useable_for_folding_p): Do not try
> to acc
On Thu, Sep 11, 2014 at 3:25 PM, Bernd Schmidt wrote:
> Bootstrapped and tested on x86_64-linux, together with the other patches.
> Ok?
This is OK.
Ciao!
Steven
On 11/09/14 14:55, Jiong Wang wrote:
On 11/09/14 14:43, Christophe Lyon wrote:
Hi Jiong,
On 9 September 2014 12:59, Ramana Radhakrishnan
wrote:
On Mon, Aug 18, 2014 at 11:31 AM, Jiong Wang wrote:
this patch enable auto-vectorization for copysignf by using vector
bit selection instruction o
On Thu, Sep 11, 2014 at 3:26 PM, Bernd Schmidt wrote:
> nvptx will be the first port to use BImode and have STORE_FLAG_VALUE==-1.
> That has exposed a bug in combine where we can end up calling
> num_sign_bit_copies for a BImode value. However, the return value is always
> 1 in that case, so it doe
On Thu, Sep 11, 2014 at 3:27 PM, Bernd Schmidt wrote:
> It turns out that we're calling eliminate_regs for global variables which
> can't possibly have eliminable regs in their decl. At that point,
> reg_eliminate can be NULL. This patch avoids unnecessary work, and allows us
> to add an assert to
Committed to branch dmalcolm/jit:
ChangeLog.jit:
* MAINTAINERS (Various Maintainers): Add myself as jit maintainer.
gcc/jit/ChangeLog.jit:
* TODO.rst (Initial Release): Update for addition of myself as
maintainer.
---
ChangeLog.jit | 4
MAINTAINERS
On 09/11/2014 02:10 PM, Yury Gribov wrote:
On 09/11/2014 01:18 PM, Richard Biener wrote:
On Thu, Sep 11, 2014 at 11:06 AM, Richard Biener
wrote:
>On Wed, Sep 10, 2014 at 10:09 AM, Yury Gribov
wrote:
>>Hi all,
>>
>>This is a second version of patch which adds a Vim config
(.local.vimrc)
>>to r
On 09/11/2014 05:55 PM, Steven Bosscher wrote:
On Thu, Sep 11, 2014 at 3:26 PM, Bernd Schmidt wrote:
nvptx will be the first port to use BImode and have STORE_FLAG_VALUE==-1.
That has exposed a bug in combine where we can end up calling
num_sign_bit_copies for a BImode value. However, the return
On Thu, Sep 11, 2014 at 6:06 PM, Bernd Schmidt wrote:
> On 09/11/2014 05:55 PM, Steven Bosscher wrote:
>>
>> On Thu, Sep 11, 2014 at 3:26 PM, Bernd Schmidt wrote:
>>>
>>> nvptx will be the first port to use BImode and have STORE_FLAG_VALUE==-1.
>>> That has exposed a bug in combine where we can end
Working on ICE debugging patch, I've noted that libiberty interface
doesn't allow to append stdout and stderr to existing files.
This small patch provides two new flags for pex_run and extends
open_write interface to handle the issue.
Does this patch look sane?
-Maxim
libiberty/ChangeLog:
2
On 09/11/2014 06:15 PM, Steven Bosscher wrote:
On Thu, Sep 11, 2014 at 6:06 PM, Bernd Schmidt wrote:
On 09/11/2014 05:55 PM, Steven Bosscher wrote:
On Thu, Sep 11, 2014 at 3:26 PM, Bernd Schmidt wrote:
nvptx will be the first port to use BImode and have STORE_FLAG_VALUE==-1.
That has exposed
Hi, Joseph,
Thanks for your review! I've added comments for new functions and
replaced POSIX subprocess interfaces with libiberty's ones.
In general, when cc1 or cc1plus ICE-es, we try to reproduce the bug by
running compiler 3 times and comparing stderr and stdout on each attempt
with respe
On 09/11/2014 12:37 PM, FX wrote:
Changing the fntype[2] looks wrong to me, as it is also used for
powi(double, int) , where the argument order matches the current
version:
Ah, sorry. I only looked at mathbuiltins.def and didn't spot the other use.
It looks like fntype[5] is actually what you
> So it looks like the following patch would be the right thing?
I would think so.
FX
On Thu, Sep 11, 2014 at 9:18 AM, Maxim Ostapenko
wrote:
>
> Working on ICE debugging patch, I've noted that libiberty interface doesn't
> allow to append stdout and stderr to existing files.
>
> This small patch provides two new flags for pex_run and extends open_write
> interface to handle the is
On Thu, Sep 11, 2014 at 6:19 PM, Bernd Schmidt wrote:
>>> What do you expect that function to do different? It returns the correct
>>> value.
>>>
>>
>> No different. Just that if you want to check whether DECL is a global
>> variable then we have a predicate for it. So why use TREE_STATIC
>> instea
On 09/11/2014 06:34 PM, Steven Bosscher wrote:
On Thu, Sep 11, 2014 at 6:19 PM, Bernd Schmidt wrote:
What do you expect that function to do different? It returns the correct
value.
No different. Just that if you want to check whether DECL is a global
variable then we have a predicate for it.
> "Jakub" == Jakub Jelinek writes:
Jakub> I fear that is going to be too expensive, because e.g. all the
Jakub> caching that dejagnu and our tcl stuff does would be gone, all
Jakub> the tests for lp64 etc. would need to be repeated for each test.
In gdb I arranged to have this stuff saved i
On Thu, 11 Sep 2014, Marc Glisse wrote:
> I don't know what kind of test you have in mind, so I added a runtime test. I
> am just guessing that it probably fails on alpha because of PR 58757, I can't
> test. Computing d+d may be even more likely to trigger potential issues, if
> that's the goal.
Hi,
On 09/11/2014 05:06 PM, Jason Merrill wrote:
Do we need a documentation update?
I agree. Something like the below would do?
Thanks,
Paolo.
2014-09-11 Paolo Carlini
PR c++/61489
* doc/invoke.texi ([-Wmissing-field-initializers]): Update.
/cp
2014-09-11
On 09/11/2014 03:06 AM, Jan Hubicka wrote:
http://kam.mff.cuni.cz/~hubicka/odr-warnings-firefox.txt
/aux/hubicka/firefox4/content/media/fmp4/ffmpeg/libav53/include/libavcodec/avcodec.h:997:0:
note: the first difference of corresponding definitions is field ‘data’
uint8_t *data[AV_NUM_DAT
OK, thanks.
Jason
> On Thu, 11 Sep 2014, Jan Hubicka wrote:
>
> > Hi,
> > this patch adds computation and streaming of mangled type names. As
> > suggested by Jason,
> > it simple calls DECL_ASSEMBLER_NAME on all names types and lets C++ supply
> > them.
> > This makes it possible to stablish precise ODR type eq
> On 09/11/2014 03:06 AM, Jan Hubicka wrote:
> >http://kam.mff.cuni.cz/~hubicka/odr-warnings-firefox.txt
>
> >/aux/hubicka/firefox4/content/media/fmp4/ffmpeg/libav53/include/libavcodec/avcodec.h:997:0:
> > note: the first difference of corresponding definitions is field ‘data’
> > uint8_t *dat
> Here is a patch I'm testing now:
Hi Jakub,
I also tested your patch to compare timings vs a newer patch (v8) I'll send soon
== patch v8 == make -j32 -k ==
check-fortran 4m58.178s
check-c++ ~10m
check-c ~10m
check 15m29.873s
== patch Jakub
check-c++ ~20m
check-fortran
On Wed, Sep 10, 2014 at 3:31 PM, Xinliang David Li wrote:
> Can you share the buildinfo reader code with the merger by defininig
> some hooks for different callbacks?
Do you mean the two blobs of code guarded by 'if (tag ==
GCOV_TAG_BUILD_INFO)' that I added here and the existing one in
gcov_exit
Yes, that is what I meant.
David
On Thu, Sep 11, 2014 at 10:09 AM, Teresa Johnson wrote:
> On Wed, Sep 10, 2014 at 3:31 PM, Xinliang David Li wrote:
>> Can you share the buildinfo reader code with the merger by defininig
>> some hooks for different callbacks?
>
> Do you mean the two blobs of co
On Thu, Sep 11, 2014 at 05:04:56PM +, VandeVondele Joost wrote:
> > Here is a patch I'm testing now:
>
> I also tested your patch to compare timings vs a newer patch (v8) I'll send
> soon
>
> == patch v8 == make -j32 -k ==
> check-fortran 4m58.178s
> check-c++ ~10m
> check-c ~10
Sorry I let this slide.
On Mon, Jul 14, 2014 at 01:54:13PM +0200, Jakub Jelinek wrote:
> On Sun, Jul 13, 2014 at 07:55:44PM +0200, Marek Polacek wrote:
> > 2014-07-13 Marek Polacek
> >
> > * ubsan.h (struct ubsan_mismatch_data):
>
> Missing description.
Fixed.
> > + gcc_assert (TREE_C
On Thu, 11 Sep 2014, Joseph S. Myers wrote:
On Thu, 11 Sep 2014, Marc Glisse wrote:
I don't know what kind of test you have in mind, so I added a runtime test. I
am just guessing that it probably fails on alpha because of PR 58757, I can't
test. Computing d+d may be even more likely to trigger
On Thu, Sep 11, 2014 at 3:00 PM, Kirill Yukhin wrote:
> Patch in the bottom extends integer max/min patterns.
> Also, it seems, like rounding variant was generated
> for maxmin patterns. Bug fixed.
>
> Bootstrapped.
> AVX-512* tests on top of patch-set all pass
> under simulator.
>
> Is it ok for
On Thu, Sep 11, 2014 at 3:16 PM, Kirill Yukhin wrote:
> Patch in the bottom extends patterns for rotate, ternlog and align.
>
> Bootstrapped.
> AVX-512* tests on top of patch-set all pass
> under simulator.
>
> Is it ok for trunk?
>
> gcc/
> * config/i386/sse.md
> (define_mode_ite
On Thu, Sep 11, 2014 at 07:26:37PM +0200, Jakub Jelinek wrote:
> right now. The patch below intends to serialize the content of the
> problematic *.exp tests (the first runtest to reach one of those will simply
> run all the tests from that *.exp file, others will skip it).
Forgotten patch below.
On Thu, Sep 11, 2014 at 11:10 AM, Uros Bizjak wrote:
> On Thu, Sep 11, 2014 at 3:00 PM, Kirill Yukhin
> wrote:
>
>> Patch in the bottom extends integer max/min patterns.
>> Also, it seems, like rounding variant was generated
>> for maxmin patterns. Bug fixed.
>>
>> Bootstrapped.
>> AVX-512* test
> And these Fortran inter-test dependencies, which Tobias told me is
> PR56408.
> For PR56408 we need some fix.
BTW, is there anything special about Fortran ? There are at least 180 test
files that contain 'dg-additional-sources' some in a very non-local way:
./objc.dg/foreach-2.m: /* {
1 - 100 of 140 matches
Mail list logo
