OK, thanks.
Jason
> > 2013-03-18 David Holsgrove
> >
> > * gcc/config/microblaze/microblaze.c (microblaze_expand_prologue):
> >Add check for flag_stack_usage to handle -fstack-usage support
> >
> > Signed-off-by: David Holsgrove
>
> Patch remains the same, please apply when ready.
The patch is incorrect,
On Sat, Jul 20, 2013 at 02:04:24AM -0400, Jason Merrill wrote:
> On 07/19/2013 03:01 PM, Marek Polacek wrote:
> >On Fri, Jul 19, 2013 at 08:50:42PM +0200, Jakub Jelinek wrote:
> >>uintptr_type_node is a C/C++/ObjC/ObjC++ FE tree. So, if you use it just
> >>in c-family/c-ubsan.c, that is just fine,
On Fri, 19 Jul 2013, Andrew Pinski wrote:
I was creating a new gimple/folding interface
Thanks.
and wanted some opinions on the interface.
typedef double_int (*nonzerobits_t)(tree var);
typedef tree (*valueizer_t)(tree var);
class gimple_combine
{
public:
gimple_combine(nonzerobits_t a, v
The code isn't exercised under normal circumstances, but still.
2013-07-20 Eric Botcazou
PR ada/57934
* gcc-interface/ada.h (CAT): Fix typo.
--
Eric Botcazou
Index: gcc-interface/ada.h
===
--- gcc-interface/ada
On 17 July 2013 20:22, Cary Coutant wrote:
>>> > Yep, the problem is where to produce the section ordering file.
>>> > The scheme is as follows:
>>> > - with -fprofile-generate instrument every function entry point and
>>> > record
>>> > time of first and last invocation of the functoin
>>>
On Sat, 20 Jul 2013, Jakub Jelinek wrote:
> Joseph, any comments?
I have no comments here.
--
Joseph S. Myers
jos...@codesourcery.com
Hello world,
the attached patch fixes two cases of unnecessary array temporaries
when vector indices were involved. When we saw something like that,
we gave up even if
- The vector indices were equal
- The vector indices didn't matter at all because, in a different
dimension, things were know
On Sat, Jul 20, 2013 at 10:19:55AM +0200, Marek Polacek wrote:
> On Sat, Jul 20, 2013 at 02:04:24AM -0400, Jason Merrill wrote:
> > On 07/19/2013 03:01 PM, Marek Polacek wrote:
> > >On Fri, Jul 19, 2013 at 08:50:42PM +0200, Jakub Jelinek wrote:
> > >>uintptr_type_node is a C/C++/ObjC/ObjC++ FE tree
While translating GCC (to Swedish), I've occasionally come across
obviously truncated strings. Often, it has been caused by multiple
lines used for the description in .opt files. I've tried to file
reports about them.
One such report I made in late 2007. In 2011 I got the suggestion to
send in
On 7/20/13 4:14 PM, Eric Botcazou wrote:
2013-03-18 David Holsgrove
* gcc/config/microblaze/microblaze.c (microblaze_expand_prologue):
Add check for flag_stack_usage to handle -fstack-usage support
Signed-off-by: David Holsgrove
Patch remains the same, please apply when ready.
The
Hi Thomas,
This is OK for trunk. Could you expand the comment to capture the two
cases without dependency. eg.
There is no dependency if the vector indices are equal or things are
known to be different in a different dimension.
Thanks for the patch!
Paul
On 20 July 2013 16:15, Thomas Koenig w
With ubsan, we ICEd in gimplify_expr e.g. on the following testcase
typedef volatile int VI;
int
foo (void)
{
VI vi = 100;
return 2 << ++vi;
}
because c_save_expr created c_maybe_const_expr which then leaked into
gimplification, oops. Fixed by calling c_fully_fold on second argument;
I'm ca
On Mon, Jul 15, 2013 at 5:43 PM, Michael Meissner
wrote:
> Are these patches ok to install?
>
> 2013-07-15 Michael Meissner
>
> * config/rs6000/vector.md (xor3): Move 128-bit boolean
> expanders to rs6000.md.
> (ior3): Likewise.
> (and3): Likewise.
> (on
On 07/09/2013 10:23 AM, Sandra Loosemore wrote:
On 06/30/2013 09:24 PM, Sandra Loosemore wrote:
Here is my third attempt at cleaning up -fstrict-volatile-bitfields.
Ping?
...and ping again.
Part 1 removes the warnings and packedp flag. It is the same as in the
last version, and has alre
Le 16/07/2013 17:16, Tobias Burnus a écrit :
> As reported in the PR, gfortran was lacking a check for the args= for
> MIN/MAX. Those are special as they accept 'infinitely' many arguments -
> while others have a finite set.
>
> Added checks:
> - Ensure that only a1=, a2=, a3= etc. is used.
> - En
Le 17/07/2013 11:02, Tobias Burnus a écrit :
> As there is again a CPU dependence:
> - David, can you have a look at config/fpu-aix.h?
> - Eric and Gerald, can you have a look at config/fpu-sysv.h?
> - Uros, can you have a look at config/fpu-387.h?
>
> All: Does on any of the systems exists a roun
On Sat, 20 Jul 2013, Marek Polacek wrote:
> Ok for ubsan branch?
I explicitly have no comments on this branch patch. When there's
something for trunk I'll review that patch as a whole.
--
Joseph S. Myers
jos...@codesourcery.com
On 07/20/2013 10:27 AM, Jakub Jelinek wrote:
So, the middle-end can only use
some other type, say build_nonstandard_integer_type (POINTER_SIZE, 1);
which often will be the same type as uintptr_type_node, but perhaps not on
all targets. It could be worth to create such a type in tree.c and stick
On Sat, 20 Jul 2013, Göran Uddeborg wrote:
> While translating GCC (to Swedish), I've occasionally come across
> obviously truncated strings. Often, it has been caused by multiple
> lines used for the description in .opt files. I've tried to file
> reports about them.
>
> One such report I made
20 matches
Mail list logo
