Would be more useful if we could use "const char * const *", but there's
a long standing bug where gcc warns about incompatible pointers when you
try to pass in "char **". We can at least constify the array itself as
gcc will not warn in that case.
include/:
2016-01-03 Mike Frysinger
This func is basically open coding the xstrdup function, so gut it
and use it directly.
2016-01-03 Mike Frysinger
* argv.c (dupargv): Replace strlen/xmalloc/strcpy with xstrdup.
---
libiberty/argv.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/libiberty/arg
Since the 3.0.3 release of gperf (made in May 2007), the generated func
has had the gnu_inline attribute applied to it. The gcc source however
has not been updated to include that which has lead to a mismatch.
In practice, this hasn't been an issue for two reasons:
(1) Before gcc-5, the default s
On Sat, Jan 2, 2016 at 11:16 AM, Marcin Kościelnicki wrote:
>
> The differences start in the __morestack calling convention. Basically,
> since pushing things on stuck is unwieldy and there's only one free
> register (%r0 could be used for static chain, %r2-%r6 contain arguments,
> %r6-%r15 are c
On 01/02/2016 01:37 AM, Vladimír Čunát wrote:
On 01/02/2016 12:13 AM, Sandra Loosemore wrote:
On 01/01/2016 12:31 PM, Vladimír Čunát wrote:
I noticed tiny typos in the docs.
(CC me with replies, please, as I'm not reading the list.)
This patch is fine with an appropriate ChangeLog entry. Gen
> On powerpc64:
>
> FAIL: gnat.dg/specs/debug1.ads scan-assembler-times DW_AT_artificial 18
>
> $ grep -c DW_AT_artificial debug1.s
> 17
Test removed.
--
Eric Botcazou
On Sat, Jan 2, 2016 at 3:21 AM, Jakub Jelinek wrote:
> On Fri, Jan 01, 2016 at 10:06:34PM -0700, Jeff Law wrote:
>> >gcc/cp/ChangeLog:
>> >
>> > * cp-array-notation.c (cp_expand_cond_array_notations): Return
>> > error_mark_node only if find_rank failed, not if it was
>> > successful.
On Wed, 16 Dec 2015, Thomas Preud'homme wrote:
> Currently, the documentation for --with-multilib-list in
> gcc/doc/install.texi only mentions sh*-*-* and x86-64-*-linux* targets.
> However, arm*-*-* targets also support this option. This patch adds
> documention for the meaning of this option f
Eric Botcazou writes:
>> I'm also seeing
>> +FAIL: gnat.dg/specs/debug1.ads scan-assembler-times DW_AT_artificial 17
>> and from what I can see in gcc-testresults, I'm not alone.
>
> Minor oversight, adjusted like so:
>
> * gnat.dg/specs/debug1.ads: Bump final count to 18.
On powerpc64:
F
libgcc/ChangeLog:
* config.host: Use t-stack and t-stack-s390 for s390*-*-linux.
* config/s390/morestack.S: New file.
* config/s390/t-stack-s390: New file.
* generic-morestack.c (__splitstack_find): Add s390-specific code.
gcc/ChangeLog:
* common/config/s3
Previously, .rodata was hardcoded. For C++ vague linkage functions,
this resulted in needlessly duplicated literals. With the new split
stack support, this resulted in link errors, due to .rodata containing
relocations to the discarded text sections.
gcc/ChangeLog:
* config/s390/s390.md
Here's my attempt at adding -fsplit-stack support for s390 targets
(bug 68191). Patches 1 and 2 fix s390-specific issues affecting split
stack code, and can be pushed independently of the main course. Patches
3 and 4 attempt to fix target-independent issues involving unconditional
jumps with side
With the new s390 split-stack support, when optimization is enabled,
the cold path of calling __morestack is likely to be moved to the
end of the function. This will result in the function ending in
split_stack_call_esa, which is an unconditional jump instruction and
part of the function prologue.
It seems at some point the .size hook was hijacked to emit some
machine-specific directives, and the actual .size directive was
forgotten. This caused problems for split-stack support, since
linker couldn't scan the function body for non-split-stack calls.
gcc/ChangeLog:
* config/s390/s3
When an unconditional jump with side effects targets an immediately
following label, rtl_tidy_fallthru_edge is called. Since it has side
effects, it doesn't remove the jump, but the label is still marked
as fallthru. This later causes a verification error. Do nothing in this
case instead.
gcc/C
On Sat, Jan 2, 2016 at 3:58 AM, Richard Biener
wrote:
> On January 2, 2016 11:32:33 AM GMT+01:00, Uros Bizjak
> wrote:
>>On Thu, Dec 31, 2015 at 4:29 PM, H.J. Lu wrote:
>>> On Thu, Dec 31, 2015 at 1:14 AM, Uros Bizjak
>>wrote:
On Wed, Dec 30, 2015 at 9:53 PM, H.J. Lu
>>wrote:
> SSE v
On 02/01/16 15:53, Matthias Klose wrote:
>>> In any case, GCJ_CXX_ABI_VERSION should be changed to not include
>>> __GNUC_MINOR__
>>> >> anymore. Maybe for the gcc-5-branch, set it unconditionally to 3 so
>>> >> that it
>>> >> won't change anymore with future releases from the gcc-5 branch?
>> >
On 02.01.2016 16:39, Andrew Haley wrote:
On 02/01/16 14:40, Matthias Klose wrote:
preparing for a test rebuild of the archive, and trying to run gcj-dbtool (from
GCC 5) with libgcj16 (from GCC 6):
$ gcj-dbtool -n /tmp/foo.db
libgcj failure: gcj linkage error.
Incorrect library ABI version dete
On 02/01/16 14:40, Matthias Klose wrote:
>
> preparing for a test rebuild of the archive, and trying to run gcj-dbtool
> (from
> GCC 5) with libgcj16 (from GCC 6):
>
> $ gcj-dbtool -n /tmp/foo.db
> libgcj failure: gcj linkage error.
> Incorrect library ABI version detected. Aborting.
>
> Abor
On 21.04.2015 16:37, Jakub Jelinek wrote:
On Tue, Apr 21, 2015 at 04:29:52PM +0200, Matthias Klose wrote:
On 04/21/2015 04:19 PM, Jakub Jelinek wrote:
On Tue, Apr 21, 2015 at 04:16:18PM +0200, Matthias Klose wrote:
On 04/21/2015 04:11 PM, Jakub Jelinek wrote:
On Tue, Apr 21, 2015 at 04:07:13P
On January 2, 2016 11:32:33 AM GMT+01:00, Uros Bizjak wrote:
>On Thu, Dec 31, 2015 at 4:29 PM, H.J. Lu wrote:
>> On Thu, Dec 31, 2015 at 1:14 AM, Uros Bizjak
>wrote:
>>> On Wed, Dec 30, 2015 at 9:53 PM, H.J. Lu
>wrote:
SSE vector arithmetic and logic instructions only accept aligned
>memor
On Sat, 2 Jan 2016 00:30:58 -0700
Jeff Law wrote:
> > That way gcc will be able to compile glibc's ld: PR/60465
> Egad. PIC on ia64 is a mess. I can kind of see what Richard was trying
> to do, but ewww. I don't think it's worth the effort to deep dive into
> the PIC support and make ia64 handl
On Thu, Dec 31, 2015 at 4:29 PM, H.J. Lu wrote:
> On Thu, Dec 31, 2015 at 1:14 AM, Uros Bizjak wrote:
>> On Wed, Dec 30, 2015 at 9:53 PM, H.J. Lu wrote:
>>> SSE vector arithmetic and logic instructions only accept aligned memory
>>> operand. This patch adds vector_memory_operand and "Bm" constr
On 2016.01.01 at 22:33 -0700, Jeff Law wrote:
> On 12/22/2015 03:04 AM, Nick Clifton wrote:
> >Hi Guys,
> >
> > The patch below fixes PR 68770 - a warning from valgrind about an
> > uninitialised value being used in the default_secondary_reload. The
> > problem turns out to the in copy_costs
> Normally we'd require a bootstrap & regression test. We're more lenient
> with patches to dead architectures.
I can do it if Sergei or others cannot though.
--
Eric Botcazou
On 01/02/2016 12:13 AM, Sandra Loosemore wrote:
> On 01/01/2016 12:31 PM, Vladimír Čunát wrote:
>> I noticed tiny typos in the docs.
>> (CC me with replies, please, as I'm not reading the list.)
>
> This patch is fine with an appropriate ChangeLog entry. Generally,
> fixing typos in documentation
On Fri, Jan 01, 2016 at 10:06:34PM -0700, Jeff Law wrote:
> >gcc/cp/ChangeLog:
> >
> > * cp-array-notation.c (cp_expand_cond_array_notations): Return
> > error_mark_node only if find_rank failed, not if it was
> > successful.
> Can you use -fdump-tree-original in the testcase and verify
27 matches
Mail list logo
