On Fri, 12 Jun 2015, Richard Biener wrote:
Not judging at all whether it is desirable or not, but you might have
hit the issue that when you want several convert?, you need to use the
spelling convert1?, convert2?, and it stops there, while here you would
probably want at least 4 (maybe 6?) fo
On Thu, Jun 11, 2015 at 8:32 AM, Fan You wrote:
> Hi,
>
> This is my first patch for GSoC project: extend shared_ptr to support
> arrays.
+ using element_type = _Tp[N];
using element_type = typename std::remove_extent_t<_Tp>; ?
> using _Deleter_type = typename conditional::value,
> _
Thanks! Committed.
On June 11, 2015 10:09:11 PM GMT+02:00, Marc Glisse
wrote:
>On Thu, 11 Jun 2015, Marek Polacek wrote:
>
>> On Thu, Jun 11, 2015 at 01:09:05PM +0200, Jakub Jelinek wrote:
>>> What about some nop type conversions in between?
>>> int
>>> fn1 (unsigned int x, unsigned int y)
>>> {
>>> int a = x;
>>
On June 12, 2015 3:28:51 AM GMT+02:00, DJ Delorie wrote:
>
>This was missed in the big intN patch set I did last year; it only
>shows up if you have a target with an N-bit type that isn't also used
>for a pointer type but is used for unwinding (which is a change I also
>have pending, hence I notic
On June 12, 2015 2:30:36 AM GMT+02:00, David Edelsohn wrote:
>This patch broke AIX bootstrap because dbxout.c was not updated for
>the XCOFF_DEBUGGING_INFO case.
OK.
Thanks
Richard.
>- David
>
>* dbxout.c (xcoff_debug_hooks): Provide a function for
>register_main_translation_unit hook.
>
>Index:
Generally, it seems like most of my comments from April haven't been
addressed yet.
@@ -3023,13 +3023,14 @@ conversion_warning (location_t loc, tree type, tree expr
Instead of adding folds here, let's make sure that the argument we pass
(e.g. from cp_convert_and_check to warnings_for_convert
This was missed in the big intN patch set I did last year; it only
shows up if you have a target with an N-bit type that isn't also used
for a pointer type but is used for unwinding (which is a change I also
have pending, hence I noticed ;). Tested on x86-64 and msp430 (with
the pending patch) wi
The crux of the issue causing PR 30044 is that, in the middle of
processing a template parameter list, current_template_parms is not
up-to-date. This causes problems particularly when we attempt to
instantiate a type that's defined within the very parameter list we are
processing. Of course, more
This patch broke AIX bootstrap because dbxout.c was not updated for
the XCOFF_DEBUGGING_INFO case.
- David
* dbxout.c (xcoff_debug_hooks): Provide a function for
register_main_translation_unit hook.
Index: dbxout.c
===
--- dbxout.c
OK. You can go ahead and commit the libbacktrace fix.
Committed in r224402.
Let's hold off on the testsuite fixes until we've got the sanitizer &
libbacktrace fixes installed.
Okay.
Martin
The attached change adds support for LABEL_REF plus CONST_INT in
pa_output_global_address
and fixes ICE compiling gcc.dg/torture/pr66123.c.
Tested on hppa2.0w-hp-hpux11.11, hppa64-hp-hpux11.11 and hppa-unknown-linux-gnu.
Committed to active branches.
Dave
--
John David Anglin dave.ang...@
This fixes two test failures when the default compiler mode is
-std=gnu++14
FAIL: 25_algorithms/headers/algorithm/synopsis.cc (test for excess errors)
FAIL: ext/profile/mutex_extensions_neg.cc (test for excess errors)
I don't really like the change to the synopsis.cc test, but I don't
think repr
Attached is an updated patch for both GCC and the manual.
The patch implements the suggested warning, -Wbuiltin-address,
that issues diagnostics for unsafe calls of the builtin address
functions. Safe calls are those with arguments 0 or 1 anywhere
in a program and argument 2 outside of the main
Hi Andre,
> please find attached an updated version of the patch. This patch simplifies
> some cases and ensures more straight line code. Furthermore was a bug in the
> interfacing routine for the _vptr->_copy() routine removed, where not the
> third
> and fourth arguments translated to be passed
On Tue, 2015-06-09 at 10:50 +0100, Ramana Radhakrishnan wrote:
>
> On 22/05/15 17:56, Torvald Riegel wrote:
> > On Fri, 2015-05-22 at 12:37 +0100, Ramana Radhakrishnan wrote:
> >> Hi,
> >>
> >> While writing atomic_word.h for the ARM backend to fix PR target/66200
> >> I
> >> thought it would make
I am checking in this change as an obvious fix. When the default int
type as added to main on this test it resulted in 'int int main' for
mips due to the ifdef for mips that is in the code. This patch fixes the
problem.
2015-06-11 Steve Ellcey
* gcc.dg/tree-prof/stringop-2.c: Fix i
Hi,
gcc.c-torture/execute/930408-1.c currently ICE on -fshort-enum target(s) because
TYPE_PACKED is not consistently set among type variants.
Bootstrapped/regtested ppc64le-linux, OK?
Honza
PR middle-end/66325
* c-decl.c (start_enum): Set TYPE_PACKED consistently among type
varia
Let's use explicit location for the C++ front end warnings, too. OK
with that change.
Jason
OK.
Jason
Hi Jason.
Attached is a new patch with the off-list corrections.
Tested on x86_64 Linux.
Aldy
commit 1775f74c2b78b1601c89befa724114d89fc2e8be
Author: Aldy Hernandez
Date: Tue Jun 9 18:07:44 2015 -0400
PR bootstrap/66448
* dwarf2out.c (check_die): Check for common duplicate a
On Thu, 11 Jun 2015, Steve Ellcey wrote:
> loongson and r8000 have the most changes, they no longer generate msub
> instructions with -mfused-madd because that instruction does not generate
> the correct NAN in some cases (the sign may be wrong). If HONOR_NANS
> is not set then they will genera
On Thu, 11 Jun 2015, Marek Polacek wrote:
On Thu, Jun 11, 2015 at 01:09:05PM +0200, Jakub Jelinek wrote:
What about some nop type conversions in between?
int
fn1 (unsigned int x, unsigned int y)
{
int a = x;
int b = y;
unsigned int c = x & y;
int d = a | b;
return (int) (c ^ d);
}
?
This patch updates MIPS to handle fused multiply and add instructions using
the standard fp-contract infrastructure. Currently MIPS handles -mfused-madd
as a target specific option and it is not affected by the -ffp-contract option.
This patch changes -mfused-madd to be an alias for -ffp-contract
On June 11, 2015 7:50:36 PM GMT+02:00, Jakub Jelinek wrote:
>On Fri, Jun 12, 2015 at 12:58:12AM +0800, pins...@gmail.com wrote:
>> This is just a bug in the older compiler. There was a change to fix
>in
>> placement new operator. I can't find the reference right now but
>this is
>> the same issue
> I have had a look at the table and the text around, and first I should
> correct myself.
> C_CHAR is 1, C_SIGNED_CHAR is 1, and the default values for len= and
> kind= are 1 as well.
> So, even if CHARACTER(KIND=C_CHAR) is what should be used as it's not
> dependent on the implementation's defaul
> > On Mon, 8 Jun 2015, Jan Hubicka wrote:
> >
> > > >
> > > > I think we should instead work towards eliminating the get_alias_set
> > > > langhook first. The LTO langhook variant contains the same handling,
> > > > btw,
> > > > so just inline that into get_alias_set and see what remains?
> >
On Fri, Jun 12, 2015 at 12:58:12AM +0800, pins...@gmail.com wrote:
> This is just a bug in the older compiler. There was a change to fix in
> placement new operator. I can't find the reference right now but this is
> the same issue as that.
I'm not claiming 4.1 is aliasing bug free, there are var
I was seeing crashes on localclass1.C for some testruns. The issue
turned out to be that we are doing better at pruning unnecessary debug
info, so we end up with 'B' on limbo_die_list and never referred to.
Let's deal with that situation.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit
> On Jun 12, 2015, at 12:51 AM, Ulrich Weigand wrote:
>
> Hello,
>
> since the new type-based pool allocator was merged, the SPU toolchain
> automated build / regression test has been failing due to crashes of
> the compiled GCC due to random memory corruption.
>
> Debugging this, it seems
On Thu, Jun 11, 2015 at 06:21:11PM +0200, Marc Glisse wrote:
> On Thu, 11 Jun 2015, Marek Polacek wrote:
>
> >>>+ (if (single_use (@2) && single_use (@3))
> >>>+ (bit_xor @0 @1)))
> >>
> >>I don't think we should use single_use here. The result is never more
> >>complicated than the original. S
Hello,
since the new type-based pool allocator was merged, the SPU toolchain
automated build / regression test has been failing due to crashes of
the compiled GCC due to random memory corruption.
Debugging this, it seems this is caused by GCC being miscompiled by
the host compiler. As one exampl
Hi,
the following patch is a quick fix for PR 66301.
eliminate_dom_walker::before_dom_children in tree-ssa-pre.c calls
dump_possible_polymorphic_call_targets when dump_enabled_p returns
true, but the function assumes dump_file is not NULL while the
predicate also returns true when alt_dump_file is
On Thu, 11 Jun 2015, Marek Polacek wrote:
+ (if (single_use (@2) && single_use (@3))
+ (bit_xor @0 @1)))
I don't think we should use single_use here. The result is never more
complicated than the original. Sure, it might increase register pressure a
bit in some cases, but we have not used t
On 11/06/15 23:32 +0800, Fan You wrote:
Hi,
This is my first patch for GSoC project: extend shared_ptr to support
arrays.
Changes are made in these files:
* libstdc++-v3/include/bits/shared_ptr_base.h : Renamed _Sp_counted_deleter
to _Sp_counted_array, changed _shared_count construct from _Sp_
Hi,
this fixes PR middle-end/65958 on the ARM, the architecture for which it was
reported, by implementing stack checking by means of probing in the back-end.
Other mainstream back-ends (alpha, i386, ia64, mips, rs6000, sparc) already
have such an implementation. The middle-end contains a gen
On Thu, Jun 11, 2015 at 05:25:30PM +0200, Marc Glisse wrote:
> On Thu, 11 Jun 2015, Marek Polacek wrote:
>
> >I have verified this transformation on a toy testcase (tried x and y
> >in the range [-1000,1000]) and it does a correct thing for all integers.
>
> Note that for pure bitop (only involvi
On June 11, 2015 5:25:30 PM GMT+02:00, Marc Glisse wrote:
>On Thu, 11 Jun 2015, Marek Polacek wrote:
>
>> I have verified this transformation on a toy testcase (tried x and y
>> in the range [-1000,1000]) and it does a correct thing for all
>integers.
>
>Note that for pure bitop (only involving &|
Hi,
On Thu, 11 Jun 2015 12:56:50, Richard Biener wrote:
>
> I also think we need to be conservative. I didn't look at the patch in detail
> to check whether we are indeed conservative here (what about offsets
> that are not visibly constant like for if (n> m) ... a[m];?).
>
we only handle constan
This is the bootstrap comparison failure on the SPARC, triggered by a CCP
change at the GIMPLE level exposing a latent issue in the back-end and
resulting in the miscompilation of cse.c at -O2. In fact it's just another
instance of http://gcc.gnu.org/ml/gcc-patches/2012-07/msg00960.html so I ha
Dear Andre and Mikael,
Thanks for the reviews and the discussion about the name of the
temporary. I went for "source" in the end. The "expr3" was merely
meant to align with the expression
Following Andre's suggestion, I left his additions to another time;
especially since the patch was headin
Hi,
On Thu, 11 Jun 2015 16:38:23, Richard Biener wrote:
>
> Sounds like a red-zone is not accounted for?
>
No, I know about the red-zone:
+#ifdef RED_ZONE_SIZE
+ HOST_WIDE_INT red_zone_size = RED_ZONE_SIZE;
+#else
+ HOST_WIDE_INT red_zone_size = 0;
+#endif
otherwise there would
The problem here was that cxx_eval_store_expression was storing the
value of the target variable in the hash table, but then
cxx_eval_call_expression was looking at ctx->ctor to find the value, and
it wasn't there. Fixed by handling full-object stores by swapping out
CONSTRUCTOR_ELTS.
Tested
On 11/06/15 23:32 +0800, Fan You wrote:
Any comments?
I haven't looked at the patch yet, but please CC all libstdc++ patches
to the libstdc++ list as well as gcc-patches, thanks.
On Tue, Jun 9, 2015 at 5:50 AM, Ramana Radhakrishnan
wrote:
>
>
> On 22/05/15 17:56, Torvald Riegel wrote:
>>
>> On Fri, 2015-05-22 at 12:37 +0100, Ramana Radhakrishnan wrote:
>>>
>>> Hi,
>>>
>>> While writing atomic_word.h for the ARM backend to fix PR target/66200
>>> I
>>> thought it would make
Hi,
This is my first patch for GSoC project: extend shared_ptr to support arrays.
Changes are made in these files:
* libstdc++-v3/include/bits/shared_ptr_base.h : Renamed
_Sp_counted_deleter to _Sp_counted_array, changed _shared_count
construct from _Sp_counted_ptr to _Sp_counted_array. Added
sp
Hi!
OpenMP 4.1 allows modifiers on the linear clause, like:
#ifdef __cplusplus
#pragma omp declare simd linear(ref(a):1) linear(val(b)) linear(uval(c))
int foo (int &a, int &b, int &c);
#else
#pragma omp declare simd linear(a:1) linear(val(b)) linear(uval(c))
int bar (int a, int b, int c);
#endif
On Thu, 11 Jun 2015, Marek Polacek wrote:
I have verified this transformation on a toy testcase (tried x and y
in the range [-1000,1000]) and it does a correct thing for all integers.
Note that for pure bitop (only involving &|^), testing the range [0,1] is
sufficient.
+/* (x & y) ^ (x | y
The testcase in the PR uses a lambda, but the issue affects local
classes as well. A simple case of a missing 'case'.
Tested x86_64-pc-linux-gnu, applying to trunk and 5.
commit 65488b9842de11454371c9d75652f58cab3465d4
Author: Jason Merrill
Date: Thu Jun 11 09:51:19 2015 -0400
PR c++/6
This patch teaches omp-expand how to utilize the optional static
argument in the gang clause. In OpenACC this corresponds to setting the
static chunk_size for acc loop. The idea here is that the user requests
'n' adjacent loop iterations to be executed by the same gang. And if two
loops inside the
On Thu, Jun 11, 2015 at 4:34 PM, Bernd Edlinger
wrote:
> Hi,
>
> On Thu, 11 Jun 2015 12:57:34 +0200, Jakub Jelinek wrote:
>>
>> On Thu, Jun 11, 2015 at 12:38:40PM +0200, Bernd Edlinger wrote:
>>> On Thu, 11 Jun 2015 10:02:03, Jakub Jelinek wrote:
IMHO the
#if 0
#endif
stuf
On 06/10/2015 05:24 PM, David Malcolm wrote:
Our current test suite is rather coarse-grained, acting at the level
of running gcc subprocesses, and verifying externally-visible
properties:
- Did the compile succeed?
- Was a particular dumpfile emitted, containing something matching
some
Hi,
On Thu, 11 Jun 2015 12:57:34 +0200, Jakub Jelinek wrote:
>
> On Thu, Jun 11, 2015 at 12:38:40PM +0200, Bernd Edlinger wrote:
>> On Thu, 11 Jun 2015 10:02:03, Jakub Jelinek wrote:
>>>
>>> IMHO the
>>> #if 0
>>> #endif
>>> stuff doesn't belong to the patch.
>>>
>>
>> I just wanted to leave a hin
On Thu, Jun 11, 2015 at 03:23:21PM +0100, Richard Biener wrote:
> I will have a look next week - mind opening a bugreport for this so
> I dont' forget?
Of course, I've opened https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66510 .
Cheers,
James
On Thu, 11 Jun 2015, James Greenhalgh wrote:
> On Thu, Jun 11, 2015 at 03:08:59PM +0100, Richard Biener wrote:
> > On Thu, 11 Jun 2015, Uros Bizjak wrote:
> >
> > > > So this turned up other issues thus the following is what I have
> > > > committed after bootstrapping and testing on x86_64-unkno
On Thu, Jun 11, 2015 at 03:08:59PM +0100, Richard Biener wrote:
> On Thu, 11 Jun 2015, Uros Bizjak wrote:
>
> > > So this turned up other issues thus the following is what I have
> > > committed after bootstrapping and testing on x86_64-unknown-linux-gnu.
> > >
> > > Richard.
> > >
> > > 2015-06-0
Hi!
Just nits, I'll defer the review to a C++ maintainer.
On Thu, Jun 11, 2015 at 03:49:48PM +0200, Andreas Krebbel wrote:
> 2015-06-11 Andreas Krebbel
>
> PR C++/33661
> * gcc/cp/decl.c (cp_finish_decl): Set assembler name for register
> asm constructs.
> * gcc/cp/pt
On Thu, 11 Jun 2015, Uros Bizjak wrote:
> > So this turned up other issues thus the following is what I have
> > committed after bootstrapping and testing on x86_64-unknown-linux-gnu.
> >
> > Richard.
> >
> > 2015-06-08 Richard Biener
> >
> > * tree-vect-stmts.c (vectorizable_load): Compute the
> So this turned up other issues thus the following is what I have
> committed after bootstrapping and testing on x86_64-unknown-linux-gnu.
>
> Richard.
>
> 2015-06-08 Richard Biener
>
> * tree-vect-stmts.c (vectorizable_load): Compute the pointer
> adjustment for gaps at the end of a SLP load g
Hi.
As explained in the PR, this patch fixes all the duplicate DIE attribute
issues seen in Darwin.
This patch fixes real problems on Linux as well, but they're silently
ignored by Linux's more permissive linker. I have enhanced check_die()
to check for these duplicate attributes in the fut
Hi,
register asm declarations currently don't work when being expanded as
part of a function template.
There appeared to be two problems:
1. When parsing a template function cp_finish_decl returns before the
asmspec is set in the var decl.
2. When expanding the template function the assembler_na
Just noticed this when playing with some testcases.
Bootstrap and regtest running on x86_64-unknown-linux-gnu.
Richard.
2015-06-11 Richard Biener
* tree-vect-stmts.c (vectorizable_load): Properly start loads
with the first element if this is grouped loads.
* gcc.dg/
On 06/11/2015 11:21 AM, Richard Biener wrote:
That sounds perfect: thank you Richard! I am about to commit the original fix
on mainline: should I still open a bugreport before commiting it to the GCC 5
branch?
Yes please.
For the record, as you already noticed, I opened PR debug/66503.
Origi
On Tue, Jun 09, 2015 at 09:36:08PM +0300, Ilya Verbin wrote:
> On Wed, Apr 29, 2015 at 14:06:44 +0200, Jakub Jelinek wrote:
> > [...] The draft requires only alloc or to
> > (or always, variants) for enter data and only from or delete (or always,
> > variants) for exit data, so in theory it is poss
On Thu, Jun 11, 2015 at 01:08:41PM +0200, Richard Biener wrote:
> If the pattern doesn't exist in fold-const.c (obviously it doesn't)
> then I think it makes sense to only add testcases to match this on
> GIMPLE (because in the long run we'd like to _not_ transform things
> in GENERIC, at least not
On Thu, Jun 11, 2015 at 01:09:05PM +0200, Jakub Jelinek wrote:
> What about some nop type conversions in between?
> int
> fn1 (unsigned int x, unsigned int y)
> {
> int a = x;
> int b = y;
> unsigned int c = x & y;
> int d = a | b;
> return (int) (c ^ d);
> }
> ? Also wonder, if some tes
Hi
Patch modified. Use %wu instead of HOST_WIDE_INT_PRINT_UNSIGNED.
Tested ok on aarch64-linux(big-endian and little-endian) with qemu.
Index: gcc/ChangeLog
===
--- gcc/ChangeLog (revision 223867)
+++ gcc/ChangeLog (worki
On Thu, Jun 11, 2015 at 01:17:47PM +0200, Eric Botcazou wrote:
> > Other than that, as I said already in the PR, I'm in favor of applying it to
> > the trunk (only, not release branches) and watching for performance and/or
> > wrong-code issues, but Eric is against it. What do others think about i
On Fri, May 15, 2015 at 03:04:27PM +0200, Torvald Riegel wrote:
> On Wed, 2015-05-06 at 17:54 +0300, Gleb Fotengauer-Malinovskiy wrote:
> > 2015-05-06 Gleb Fotengauer-Malinovskiy
> >
> > PR libitm/61164
> > * local_atomic (__always_inline): Rename to...
> > (__libitm_always_inline):
Hi,
This is a follow-up to Jim Wilson's patch fixing ICE's with -march=armv8-a+nofp,
and the discussion here:
https://gcc.gnu.org/ml/gcc-patches/2015-06/msg00177.html
The first patch improves the error messages to describe what kind of code caused
the problem, and to error rather than "sorry" (
> Other than that, as I said already in the PR, I'm in favor of applying it to
> the trunk (only, not release branches) and watching for performance and/or
> wrong-code issues, but Eric is against it. What do others think about it?
Yes, I'm against it, I think that the patch will introduce more i
On Thu, Jun 11, 2015 at 01:04:32PM +0200, Marek Polacek wrote:
> This patch introduces a new pattern for the match-and-simplify
> machinery.
>
> I have verified this transformation on a toy testcase (tried x and y
> in the range [-1000,1000]) and it does a correct thing for all integers.
>
> The
On Thu, 11 Jun 2015, Marek Polacek wrote:
> This patch introduces a new pattern for the match-and-simplify
> machinery.
>
> I have verified this transformation on a toy testcase (tried x and y
> in the range [-1000,1000]) and it does a correct thing for all integers.
>
> The asm diff for fn1 is
This patch introduces a new pattern for the match-and-simplify
machinery.
I have verified this transformation on a toy testcase (tried x and y
in the range [-1000,1000]) and it does a correct thing for all integers.
The asm diff for fn1 is
- andl%esi, %eax
- orl %edi, %esi
so
On 06/02/2015 04:11 PM, Marat Zakirov wrote:
On 05/26/2015 05:03 PM, Marat Zakirov wrote:
On 05/20/2015 10:01 AM, Marat Zakirov wrote:
On 05/12/2015 02:16 PM, Marat Zakirov wrote:
On 04/07/2015 03:22 PM, Jakub Jelinek wrote:
How are the automatic misaligned variables different from say h
On Thu, Jun 11, 2015 at 12:38:40PM +0200, Bernd Edlinger wrote:
> On Thu, 11 Jun 2015 10:02:03, Jakub Jelinek wrote:
> >
> > IMHO the
> > #if 0
> > #endif
> > stuff doesn't belong to the patch.
> >
>
> I just wanted to leave a hint, how I debugged this function, and how
> to assess the performance
On Thu, Jun 11, 2015 at 12:38 PM, Bernd Edlinger
wrote:
> Hi,
>
> On Thu, 11 Jun 2015 10:02:03, Jakub Jelinek wrote:
>>
>> IMHO the
>> #if 0
>> #endif
>> stuff doesn't belong to the patch.
>>
>
> I just wanted to leave a hint, how I debugged this function, and how
> to assess the performance of th
On 4 June 2015 at 14:36, Renlin Li wrote:
> Hi Marcus,
>
> Sorry for the delay. I have come up with an updated patch. Two test cases
> are added to check against the limit.
>
> __ARM_ALIGN_MAX_STACK_PWR is hard coded into 16.
> __ARM_ALIGN_MAX_PWR is hard coded into 28 which is the maximum allow
Hi,
I have been looking into this issue, which should be rather easy to
solve: the problem seems that in a template we are mishandling ~ as a
bitwise complement operator (vs destructor introducer). We end up here
in cp_parser_unqualified_id:
type_decl
= cp_parser_class_name
Hi,
On Thu, 11 Jun 2015 10:02:03, Jakub Jelinek wrote:
>
> IMHO the
> #if 0
> #endif
> stuff doesn't belong to the patch.
>
I just wanted to leave a hint, how I debugged this function, and how
to assess the performance of the decision that is taken here.
I mean, the boot-strap would certainly pa
On Thu, 11 Jun 2015, Marek Polacek wrote:
> A cleanup patch to make the code more readable.
>
> Bootstrapped/regtested on x86_64-linux, ok for trunk?
Ok.
Thanks,
Richard.
> 2015-06-11 Marek Polacek
>
> * match.pd: Use single_use throughout.
>
> diff --git gcc/match.pd gcc/match.pd
>
On Thu, Jun 11, 2015 at 11:49 AM, Kumar, Venkataramanan
wrote:
> Hi Maintainers,
>
> This patch adds support for new MONITORX and MWAITX instructions and also
> enables them via builtins.
> The ISA is enabled by new -mmwaitx option and is available for AMD bdver4
> target (-march=bdver4).
>
> M
A cleanup patch to make the code more readable.
Bootstrapped/regtested on x86_64-linux, ok for trunk?
2015-06-11 Marek Polacek
* match.pd: Use single_use throughout.
diff --git gcc/match.pd gcc/match.pd
index 48358a8..33fa717 100644
--- gcc/match.pd
+++ gcc/match.pd
@@ -301,7 +301,7
On 18/05/15 11:26, Kyrill Tkachov wrote:
Hi all,
When using the short Thumb2 IT blocks we want to also restrict ifcvt so that it
will not end up generating a number of back-to-back cond_execs
that will later end up being back to back single-instruction IT blocks.
Branching over them should b
On 27/05/15 11:25, Kyrill Tkachov wrote:
Ping.
Here is the rebased (and retested) patch after Christian's series.
Thanks,
Kyrill
On 18/05/15 11:26, Kyrill Tkachov wrote:
Hi all,
When using the short Thumb2 IT blocks we want to also restrict ifcvt so that it
will not end up generating a nu
Hi Maintainers,
This patch adds support for new MONITORX and MWAITX instructions and also
enables them via builtins.
The ISA is enabled by new -mmwaitx option and is available for AMD bdver4
target (-march=bdver4).
MONITORX and MWAITX implements same functionality as old MONITOR and MWAIT.
Ping.
Thanks,
Kyrill
On 04/06/15 16:59, Kyrill Tkachov wrote:
Ping.
https://gcc.gnu.org/ml/gcc-patches/2015-05/msg02405.html
Thanks,
Kyrill
On 27/05/15 11:25, Kyrill Tkachov wrote:
Ping.
Here is the rebased (and retested) patch after Christian's series.
Thanks,
Kyrill
On 18/05/15 11:26, Ky
Hello!
We can use MEMMODEL_BASE_MASK here to avoid a couple of similar cases.
2015-06-11 Uros Bizjak
* emit-rtl.c (need_atomic_barrier_p): Mask model with
MEMMODEL_BASE_MASK. Remove MEMMODEL_SYNC_* cases.
Tested on x86_64-linux-gnu {,-m32}.
OK for mainline?
Uros.
Index: emit-rtl.c
On 10 June 2015 at 03:46, weixiangyu wrote:
> Updated patches were attached. Rebased on the latest 4.9 branch.
> Tested on aarch64-linux (big-endian and little-endian) with qemu.
> OK for 4.9?
Hi,
> And the second one:
The original r215046 mainline commit contains a test case that is
omitted f
On Thu, 11 Jun 2015, Pierre-Marie de Rodat wrote:
> On 06/11/2015 11:06 AM, Richard Biener wrote:
> > FYI, I decided to backport the fix causing this regression to the
> > 4.8 branch today, guarded with in_lto_p, thus eliminating the effect
> > on non-LTO links. The adjusted patch looks like the
On 06/11/2015 11:06 AM, Richard Biener wrote:
FYI, I decided to backport the fix causing this regression to the
4.8 branch today, guarded with in_lto_p, thus eliminating the effect
on non-LTO links. The adjusted patch looks like the following and
I'll also adjust the 4.9 branch accordingly, leav
Hi,
this fixes a reload problem with match_dup's on commutative operands.
Bootstrapped and regtested on x86-64, ppc64, and s390x.
Ok?
Bye,
-Andreas-
2015-06-11 Andreas Krebbel
PR rtl-optimization/66306
* reload.c (find_reloads): Swap the match_dup info for
commutat
On Wed, 10 Jun 2015, Pierre-Marie de Rodat wrote:
> On 06/10/2015 03:36 PM, Richard Biener wrote:
> > Hmm, yes. It meant to break after the first ;) (without LTO
> > there usually is only one TU decl, apart from Java I think).
> > The hunk isn't in mainline because it was part of an experimental
On 10 June 2015 at 11:06, weixiangyu wrote:
> Another backport patch which fixes a csmith ICE problem. Rebased on the
> latest 4.9 branch.
> Tested ok on aarch64-linux with qemu.
>
Hi, The attached patch contains a ChangeLog diff but no code diff.
The patch r210497 on mainline is an adjustment t
Hi!
The latest spec renamed modifier argument to chunk_size.
Only for Fortran this is actually a user visible change, but for consistency
I've renamed it everywhere.
2015-06-11 Jakub Jelinek
* libgomp.h (struct gomp_task_icv): Rename
run_sched_modifier field to run_sched_chunk
On Thu, Jun 11, 2015 at 09:42:38AM +0200, Bernd Edlinger wrote:
> it was exactly to the day one year ago, when I posted this patch the first
> time:
> [PATCH] PR rtl-optimization/61047:
> https://gcc.gnu.org/ml/gcc-patches/2014-06/msg00996.html
>
> The PR was suspended, but the discussion did no
On Wed, 10 Jun 2015, Pierre-Marie de Rodat wrote:
> On 06/10/2015 03:36 PM, Richard Biener wrote:
> > Hmm, yes. It meant to break after the first ;) (without LTO
> > there usually is only one TU decl, apart from Java I think).
> > The hunk isn't in mainline because it was part of an experimental
Hi,
it was exactly to the day one year ago, when I posted this patch the first time:
[PATCH] PR rtl-optimization/61047:
https://gcc.gnu.org/ml/gcc-patches/2014-06/msg00996.html
The PR was suspended, but the discussion did not stop. And I personally still
see a bug like this
as an in-acceptable
Hi Cesar!
On Wed, 10 Jun 2015 14:35:26 -0700, Cesar Philippidis
wrote:
> This patch addresses a bug where the c and c++ front ends would ICE [...]
Thanks!
The following also doesn't look quite appropriate:
$ cat < ../d.f
IMPLICIT NONE
INTEGER X
!$ACC PAR
99 matches
Mail list logo
