Hi,
The test-case plugin/ggcplug.c was failing due to flattening of tree.h
and tree-core.h.
Test-case was incorrect because it included gcc-plugin.h after tree.h whereas
gcc-plugin.h should be the first header to be included by plugins.
OK to commit ?
Thank you,
Prathamesh
Index: gcc/testsuite/gcc
On Tue, Nov 11, 2014 at 6:47 AM, Marcus Shawcroft
wrote:
> On 30 October 2014 08:54, Gopalasubramanian, Ganesh
> wrote:
>
>> 2014-10-30 Ganesh Gopalasubramanian
>
> Check the whitespace in your ChangeLog line.
>
>> * config/arm/types.md (define_attr "type"): Add prefetch.
>
> The existi
I've checked in this patch to fix some over-full hboxes (text
overflowing the right margin) in the PDF version of the GCC manual.
More boring tech-writer stuff. :-)
-Sandra
2015-01-10 Sandra Loosemore
gcc/
* doc/invoke.texi (Option Summary): Break long lines.
[(-f
Matthew Fortune writes:
> Richard Sandiford writes:
>> Jeff Law writes:
>> > On 01/09/15 04:32, Robert Suchanek wrote:
>> >> Hi Steven/Vladimir,
>> >>
>> >>> It's hard to say what the correct fix should be, but it sounds like
>> >>> the address you get after the substitutions should be simplifi
Hi!
On Wed, 12 Nov 2014 15:43:06 -0500, David Malcolm wrote:
> On Wed, 2014-11-12 at 21:30 +0100, Jakub Jelinek wrote:
> > On Wed, Nov 12, 2014 at 03:22:21PM -0500, David Malcolm wrote:
> > > On Wed, 2014-11-12 at 14:47 +0100, Jakub Jelinek wrote:
> > > > On Wed, Nov 12, 2014 at 08:33:34AM -0500,
On 8 January 2015 at 17:52, Richard Biener wrote:
> On Sun, 21 Dec 2014, Prathamesh Kulkarni wrote:
>
>> Hi,
>> I removed printing "for expression:" from print_matches. I think it
>> is out of place tvim here and we call print_matches after lowering.
>> OK to commit ?
>
> Hum, it's now a very simp
Richard Sandiford writes:
> Jeff Law writes:
> > On 01/09/15 04:32, Robert Suchanek wrote:
> >> Hi Steven/Vladimir,
> >>
> >>> It's hard to say what the correct fix should be, but it sounds like
> >>> the address you get after the substitutions should be simplified
> >>> (folded).
> >>
> >> Comi
On Fri, Jan 9, 2015 at 5:56 PM, H.J. Lu wrote:
> On Fri, Jan 9, 2015 at 12:12 PM, Magnus Granberg wrote:
>> fredag 09 januari 2015 13.00.14 skrev Daniel Micay:
>>> On 09/01/15 12:49 PM, Joseph Myers wrote:
>>> > On Fri, 9 Jan 2015, Daniel Micay wrote:
>>> >>> --with-specs="%{pie|fpic|fPIC|fpie|f
Hi all,
attached patch fixes the bug reported in pr 60334. The issue here was that the
function's result being (a pointer to) a deferred length char array. The string
length for the result value was wrapped in a local variable, whose value was
never written back to the string length of the result.
On Wednesday 31 December 2014, Jakub Jelinek wrote:
> On Wed, Dec 31, 2014 at 01:28:47PM +0100, Allan Sandfeld Jensen wrote:
> > I recently wanted to use multiversioning for BMI2 specific extensions
> > PDEP/PEXT, and noticed it wasn't there. So I wrote this patch to add it,
> > and also added AES,
Sorry for the slow response. Jeff has approved the patch in the
meantime, but I didn't want to go ahead and apply it while there
was still disagreement...
Eric Botcazou writes:
>> Please be more specific though. If you don't think the patch is correct,
>> what do you think the requirement shoul
Jeff Law writes:
> On 01/09/15 04:32, Robert Suchanek wrote:
>> Hi Steven/Vladimir,
>>
>>> It's hard to say what the correct fix should be, but it sounds like
>>> the address you get after the substitutions should be simplified
>>> (folded).
>>
>> Coming back to the original testcase and re-analyz
>> If unused on trunk, why would we commit it there?
>> When your branch is merged, you'll merge it along. Otherwise that defeats
>> the purpose of working on a branch, unless I misunderstand something...
>
> This patch is not branch-specific.
As far as I understand, we don’t add unused code to
When using word-wide CAS to emulate atomic fetch-and-op, addresses should
be word-aligned to avoid exceptions on some targets.
The problem manifested in a new port I'm working on as a failure in test
gcc.dg/atomic/stdatomic-op-1.c, and I've confirmed that this patch
fixes it. x86_64-unknown-linux
I'm committing this patch which correctly forces a flag on instead of
off.
AG
2015-01-10 Anthony Green
* config/moxie/moxie.c (moxie_option_override): Fix forcing of
mul.x availability for moxiebox configuration.
Index: gcc/config/moxie/moxie.c
=
On 01/10/2015 10:03 AM, Chen Gang S wrote:
> The related commit is "275e275 IPA ICF: target and optimization flags
> comparison.". For sem_function::equals_private(), fix the typo issue,
> and for target_opts_for_fn(), fix access NULL issue.
>
> For cross compiling h8300, it will cause the issue b
Rainer Orth writes:
> Chen Gang S writes:
>
>> The related commit is "275e275 IPA ICF: target and optimization flags
>> comparison.". For sem_function::equals_private(), fix the typo issue,
>> and for target_opts_for_fn(), fix access NULL issue.
>
> The NULL pointer dereference issue also broke
Chen Gang S writes:
> The related commit is "275e275 IPA ICF: target and optimization flags
> comparison.". For sem_function::equals_private(), fix the typo issue,
> and for target_opts_for_fn(), fix access NULL issue.
The NULL pointer dereference issue also broke Solaris/SPARC bootstrap...
> T
The related commit is "275e275 IPA ICF: target and optimization flags
comparison.". For sem_function::equals_private(), fix the typo issue,
and for target_opts_for_fn(), fix access NULL issue.
For cross compiling h8300, it will cause the issue below:
[root@localhost h8300]# cat fp-bit.i
__inl
19 matches
Mail list logo
