Hi!
On Thu, 20 Jun 2013 15:08:16 -0700, Ian Lance Taylor i...@airs.com wrote:
Thomas Schwinge tho...@codesourcery.com writes:
On Sun, 05 May 2013 18:55:09 -0700, Ian Lance Taylor i...@airs.com wrote:
Thomas Schwinge tho...@codesourcery.com writes:
libgcc/
* fp-bit.c
Hi all,
With r200197 the test pr46975.c now fails because the code:
/* { dg-options -mthumb -Os } */
int foo (int s)
{
return s == 1;
}
now generates:
0: f1a0 0001 sub.w r0, r0, #1
4: fab0 f080 clz r0, r0
8: 0940lsrsr0, r0, #5
a:
Richard Biener rguent...@suse.de writes:
+ register const void **jump_table asm (r12);
That can't work.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
And now for something completely different.
2013/6/20 Richard Biener rguent...@suse.de:
2013-06-20 Richard Biener rguent...@suse.de
PR tree-optimization/57584
* tree-ssa-loop-niter.c (expand_simple_operations): Avoid including
SSA names into the expanded expression that take part in
abnormal
Hi,
looks like we implemented LWG 630 incompletely, not updating:
valarray::operator=(const _Expr)
together with the copy assignment operator. The inconsistency clearly
shows up eg when we try to assign the result of an arithmetic binary
operation.
Tested x86_64-linux. Gaby, any
Hi Eric,
Can you please help to review the general idea and this patch for zero
sign extension elimination with VRP?
Thanks,
Kugan
On 17/06/13 11:01, Kugan wrote:
Can you please help to review this patch? Richard reviewed the original
patch and asked it to be split into two parts. Also,
On 21/06/13 09:49, Kyrylo Tkachov wrote:
Hi all,
With r200197 the test pr46975.c now fails because the code:
/* { dg-options -mthumb -Os } */
int foo (int s)
{
return s == 1;
}
now generates:
0: f1a0 0001 sub.w r0, r0, #1
4: fab0 f080 clz r0, r0
Hi all,
This patch adjusts the patterns in thumb2.md to conform with -mrestrict-it.
16-bit alternatives are added, patterns that explicitly generate IT blocks
that don't conform are disabled or replaced with appropriate patterns for
arm_restrict_it. A new pattern thumb2_cond_arith_strict_it is
Hi all,
This is the final patch in the series. It adjusts patterns in arm.md that do
arithmetic operations and comparisons. We add alternatives for 16-bit
encodings to the patterns. Some alternatives and patterns are disabled for
arm_restrict_it or their cond_exec variants.
The Pd constraint is
On 20/06/13 02:00, Vladimir Makarov wrote:
I hope the following patch fixes
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57604
Although I have no specific hardware to check this.
The patch also adds a comment about one recent change as it was done in
the same function.
The patch was
... grrr, I attached the wrong testcase, isn't testing anything.
Corrected below.
Paolo.
///
Index: include/std/valarray
===
--- include/std/valarray(revision 200268)
+++ include/std/valarray
On 08/08/2012 11:08 PM, Dodji Seketeli wrote:
OK to commit?
Looks good, but what sets LIBXML2_NEW_BUFFER ?
Andrew.
On Fri, Jun 21, 2013 at 12:13:35PM +0100, Andrew Haley wrote:
On 08/08/2012 11:08 PM, Dodji Seketeli wrote:
OK to commit?
Looks good, but what sets LIBXML2_NEW_BUFFER ?
I lack context but I think I can answer that one :)
LIBXML2_NEW_BUFFER is a libxml2 public macro from libxml/tree.h
/*
Hi,
As mentioned be Jakub, Intel Spec introduces single-underscored
intrinsics for bextr insn which takes different arguments.
Patch introduces intrinsics and tests.
ChangeLog:
2013-06-20 Kirill Yukhin
kirill.yuk...@intel.com
On 06/21/2013 12:19 PM, Daniel Veillard wrote:
On Fri, Jun 21, 2013 at 12:13:35PM +0100, Andrew Haley wrote:
On 08/08/2012 11:08 PM, Dodji Seketeli wrote:
OK to commit?
Looks good, but what sets LIBXML2_NEW_BUFFER ?
I lack context but I think I can answer that one :)
[list copied]
On 06/20/13 11:20, Jakub Jelinek wrote:
On Wed, Jun 19, 2013 at 05:08:38PM -0500, Aldy Hernandez wrote:
On 06/19/13 16:43, Jakub Jelinek wrote:
On Wed, Jun 19, 2013 at 04:39:52PM -0500, Aldy Hernandez wrote:
Jumps are disallowed into or out of the body of the for loop
On 06/21/2013 01:00 PM, Andreas Krebbel wrote:
On 20/06/13 02:00, Vladimir Makarov wrote:
I hope the following patch fixes
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57604
Although I have no specific hardware to check this.
The patch also adds a comment about one recent change as it was
I think I will continue to work from SVN branches, because I'm a lot
more familiar with that process. I'm also going to start working on a
couple of different checkouts of the c++-concepts branch
independently, so this should be a little easier for me.
I can move those patches over to git and
On Fri, Jun 21, 2013 at 12:53 AM, Alan Modra amo...@gmail.com wrote:
A number of places in the rs6000 backend assume the value for a vec
splat can be found at element nunits-1 of a vector constant, which is
wrong for little-endian. This patch fixes them and the ICE found
when running
On Fri, Jun 21, 2013 at 07:16:56AM -0500, Aldy Hernandez wrote:
I have done as suggested, and cleaned things up along the way.
I believe this is the last remaining TODO on my Cilk Plus pragma
simd list. Everything else is dependent on OMP4.
Is this what you had in mind?
Roughly, yes.
David: Can you have a look at libgfortran/config/fpu-aix.h - Thanks!
Uros: Can you have a look at libgfortran/config/fpu-387.h - Thanks!
The patch silently changes libgfortran/config/fpu-sysv.h as well, breaking
Solaris in the process:
In file included from /nile.build/botcazou/gcc-
Paolo Carlini paolo.carl...@oracle.com writes:
| ... grrr, I attached the wrong testcase, isn't testing
| anything. Corrected below.
|
| Paolo.
|
| ///
OK.
-- Gaby
Initial pass on diagnostics for constraints. The general approach is
to recurse through a requirement expression searching for constraints
that have failed, generating as precise a message as possible.
Admittedly, these will require some polishing (indentation, messages,
formatting, choosing a
On Fri, Jun 21, 2013 at 1:26 PM, Kirill Yukhin kirill.yuk...@gmail.com wrote:
Hi,
As mentioned be Jakub, Intel Spec introduces single-underscored
intrinsics for bextr insn which takes different arguments.
Patch introduces intrinsics and tests.
ChangeLog:
2013-06-20 Kirill Yukhin
In order to ensure that ALLOCATED(var) works, we have to allocate at
least one byte. While malloc(0) is permitted, it is system depended
whether it returns NULL or a unique non-NULL pointer.
Build and regtested on x86-64-gnu-linux.
OK for the trunk?
Tobias
2013-06-21 Tobias Burnus
Andrew Sutton andrew.n.sut...@gmail.com writes:
| Changes are pushed in git branch asutton/c++-concepts. The Changelog
| is below
Andrew, please can you send me a diff? When reading emails, it really is
much easier for me that way. Thanks,
-- Gaby
On Fri, Jun 21, 2013 at 05:11:39PM +0200, Uros Bizjak wrote:
Is it ok to install?
This is OK for mainline.
BTW: There are many other single-underscore prefixed intrinsics [1]
besides _bextr_*. Perhaps you should also add these to the intrinsics
header, then the complete header could be
On Fri, Jun 21, 2013 at 5:19 PM, Jakub Jelinek ja...@redhat.com wrote:
On Fri, Jun 21, 2013 at 05:11:39PM +0200, Uros Bizjak wrote:
Is it ok to install?
This is OK for mainline.
BTW: There are many other single-underscore prefixed intrinsics [1]
besides _bextr_*. Perhaps you should also
case NE_EXPR:
- if (!flag_enable_cilk)
+ /* NE_EXPR is only allowed for Cilk Plus loops. */
+ if (flag_enable_cilk
+gimple_omp_for_kind (for_stmt) == GF_OMP_FOR_KIND_CILKSIMD)
+ break;
+ else
gcc_unreachable ();
- /*
Shoot. Forgot to attach the patch...
Andrew
On Fri, Jun 21, 2013 at 10:17 AM, Gabriel Dos Reis g...@axiomatics.org wrote:
Andrew Sutton andrew.n.sut...@gmail.com writes:
| Changes are pushed in git branch asutton/c++-concepts. The Changelog
| is below
Andrew, please can you send me a diff?
This patch extends the already existing end-of-scope finalization to
nonallocatables.
Note: The patch only handles finalization of unsaved local variables
whose type has a finalizer (including finalizable nonallocatable
components or finalizers in the ancestor). In that case, the finalizer
On 06/20/2013 04:39 PM, Iyer, Balaji V wrote:
I couldn't put them into 1 structure, so I made 2 structures holding the
following information: array notation triplet information and array notation
expansion loop's information. It is fixed in the patch attached.
Excellent, thanks. One thing
On Fri, 21 Jun 2013, Thomas Schwinge wrote:
Joseph suggested these two bug-fix commits (trunk r198621 and r198622)
should be applied to earlier release branches, too. OK?
Joseph, which release branches would you like me to commit these two
patches to?
4.7 and 4.8 (subject of course to
While testing it I noticed that the final executable
is larger with your patch then with mine. Here are the sizes of the
bare-metal executables I created using the same flags I sent you
earlier, the first has no switch optimization, the second one uses my
plugin optimization, and the third
Ping... These libgfortran changes are done the same way as libstdc++
so I hope they are OK.
Steve Ellcey
sell...@mips.com
From sell...@mips.com Tue Jun 4 12:49:55 2013
This patch allows me to build libgfortran for a cross-compiling toolchain
using newlib. Currently the checks done by
-Original Message-
From: Richard Henderson [mailto:r...@redhat.com]
Sent: Friday, June 21, 2013 12:11 PM
To: Iyer, Balaji V
Cc: Aldy Hernandez; gcc-patches@gcc.gnu.org; Jason Merrill
(ja...@redhat.com)
Subject: Re: [PATCH] Cilk Plus Array Notation for C++
On 06/20/2013 04:39
On 06/21/2013 09:59 AM, Iyer, Balaji V wrote:
After I remove that field, will it be OK for trunk?
Yes.
r~
In Go a function named _ does not need to be emitted, but it does need
to be compiled up to the point of the middle-end in case it has any
errors. The gccgo frontend was just skipping the function entirely.
This patch from Rémy Oudompheng fixes that. Bootstrapped and ran Go
testsuite on
case NE_EXPR:
- if (!flag_enable_cilk)
+ /* NE_EXPR is only allowed for Cilk Plus loops. */
+ if (flag_enable_cilk
Very weird name of a flag. Should have been flag_cilk or flag_cilkplus
IMHO.
I know. It was already there from Balaji's first iteration with
Le 21/06/2013 17:14, Tobias Burnus a écrit :
In order to ensure that ALLOCATED(var) works, we have to allocate at
least one byte. While malloc(0) is permitted, it is system depended
whether it returns NULL or a unique non-NULL pointer.
Build and regtested on x86-64-gnu-linux.
OK for the
Attached is the stubbed out parsing for requires expressions. I plan
on implementing semantics next.
I haven't pushed this into a git branch since its a completely
separate change from the previous patch. Should I create a new branch
for separate work?
Changelog:
2013-06-21 Andrew Sutton
Here is an updated version of Tom's if-to-switch conversion pass that
was originally posted here:
http://gcc.gnu.org/ml/gcc-patches/2013-01/msg01210.html.
I corrected a build problem with ARM by including tm_p.h and an ICE
caused by NULL_TREE argument being passed to fold_binary () inside
On Fri, 2013-06-21 at 17:43 +0100, James Greenhalgh wrote:
So to my mind, this is all far too tied up in pass ordering details to
resolve. Given that all the threading opportunities for my patch are found
in dom1 and how fragile the positioning of dom1 is, there is not a great
deal I can do
Le 21/06/2013 17:39, Tobias Burnus a écrit :
This patch extends the already existing end-of-scope finalization to
nonallocatables.
Note: The patch only handles finalization of unsaved local variables
whose type has a finalizer (including finalizable nonallocatable
components or finalizers
Steve Ellcey wrote:
Ping... These libgfortran changes are done the same way as libstdc++
so I hope they are OK.
OK - Thanks for the patch. (I was hoping that some configure maintainer
would do the deed.)
Tobias
From sell...@mips.com Tue Jun 4 12:49:55 2013
This patch allows me to build
Andrew Sutton andrew.n.sut...@gmail.com writes:
| Shoot. Forgot to attach the patch...
|reinit_cxx_pp ();
| - dump_template_decl (TREE_PURPOSE (p), flags);
| + if (decl)
| +{
| + dump_template_decl (decl, flags);
|pp_cxx_whitespace (cxx_pp);
| +}
Watch out for
Andrew Sutton andrew.n.sut...@gmail.com writes:
| Attached is the stubbed out parsing for requires expressions. I plan
| on implementing semantics next.
See comments below.
| I haven't pushed this into a git branch since its a completely
| separate change from the previous patch. Should I
This patch prevents integer-underflow of badness computation in ipa-inline.
Bootstrapped and passed regression tests.
OK for trunk?
Thanks,
Dehao
gcc/ChangeLog:
2013-06-21 Dehao Chen de...@google.com
* ipa-inline.c (edge_badness): Fix integer underflow.
Index: gcc/ipa-inline.c
ping ^3
Thx,
Dehao
On Sat, Jun 15, 2013 at 9:48 AM, Dehao Chen de...@google.com wrote:
ping ^2
On Thu, Jun 6, 2013 at 9:22 PM, Dehao Chen de...@google.com wrote:
ping...
On Tue, Jun 4, 2013 at 10:02 AM, Dehao Chen de...@google.com wrote:
Hi, Dodji,
Thanks for helping update the
49 matches
Mail list logo
