Hi Steve,
>> The second part catches the case when the user supplies more
>> digits than appropriate for the number. More often than not,
>> this is a KIND error.
>>
>
> Does the above issue warnings for
>
> real(knd), parameter :: pi = 3.1415926535897932384626433832795029_knd
>
> module foo
Found today when deleting "S" constraint, unused after a local patch.
rs6000/vsx.md:1867: error: undefined machine-specific constraint at this point:
"Sa>,"
That can't be good says I. An over-enthusiastic search and replace
by the look of it. Bootstrapped and regression tested
powerpc64le-linux.
On 30/05/15 14:54, Jeff Law wrote:
> On 05/29/2015 12:32 AM, Kugan wrote:
>
> PR target/65768
> * cprop.c (try_replace_reg): Check cost of constants before
> propagating.
>>> I should have also noted, fresh bootstrap & regression test is needed
>>> too.
>>
>> Thanks Jeff
Another error caught by ubsan.
Tested powerpc64le-linux, committed to trunk.
commit 3415b9186469cf4b94fa2f141c6e69e5db77f118
Author: Jonathan Wakely
Date: Sun May 31 22:40:28 2015 +0100
PR libstdc++/66354
* include/bits/stl_algobase.h (__fill_a): Check length before calling
me
On Sun, May 31, 2015 at 11:36:17PM +0200, Thomas Koenig wrote:
>
> The second part catches the case when the user supplies more
> digits than appropriate for the number. More often than not,
> this is a KIND error.
>
Does the above issue warnings for
cat consts.def
real(knd), parameter :: p
Jan changed TYPE_METHODS to be present only on the main variant so a couple of
predicates in c-ada-spec.c need to be adjusted accordingly.
Tested on x86_64-suse-linux, applied on the mainline as obvious.
2015-05-31 Eric Botcazou
* c-ada-spec.c (is_tagged_type): Test for TYPE_METHODS
Hello world,
please find attached a rather lengthy patch, which attempts to deal
with warnings for conversions in Fortran once and for all (one can
hope ... :-)
The patch has two parts.
One part moves all the checking for conversion into the
gfc_2 functions. The checks are made much more
extens
> I come that far on Sparc Solaris 10:
>
> Comparing stages 2 and 3
> warning: gcc/cc1plus-checksum.o differs
> warning: gcc/cc1-checksum.o differs
> Bootstrap comparison failure!
> gcc/fortran/symbol.o differs
> gcc/builtins.o differs
> gcc/real.o differs
> gcc/ubsan.o differs
> libdecnumber/deci
On 05/30/2015 08:52 PM, Aldy Hernandez wrote:
On 05/29/2015 03:33 PM, Jason Merrill wrote:
On 05/29/2015 03:26 PM, Richard Biener wrote:
ISTR I had to mark the gimple reg used for the bound as
non-DECL_IGNORED for the LTO stuff.
Let's go with that, then.
Well, I did play around with that op
When we are actually evaluating an NSDMI in a constexpr constructor,
ctx->ctor has the type of the complete object, but when we're just
checking whether the NSDMI by itself is constant, we ctx->ctor just has
the type of the data member, so references to other data members will
end up looking at
OK, thanks.
Jason
Hi Jason,
On 30.05.15 11:27, Andreas Tobler wrote:
On 29.05.15 19:18, Steve Ellcey wrote:
On Thu, 2015-05-28 at 23:54 +0200, Eric Botcazou wrote:
This patch restores bootstrap on i386-*-freebsd*.
The build was failing after the introduction of -std=c++98
configure/build flag. The -std=c++98 e
On 28.05.15 23:54, Eric Botcazou wrote:
This patch restores bootstrap on i386-*-freebsd*.
The build was failing after the introduction of -std=c++98
configure/build flag. The -std=c++98 enables strict_ansi and on FreeBSD
the libc function atoll is not defined for this.
Solaris (x86 and SPARC) i
> 2015-05-30 Eric Botcazou
>
> * adaint.c: Test for __linux__ instead of linux and __sun__ instead
> of sun. Add missing leading underscore to AIX. Remove #elif 0.
> * adaint.h: Likewise.
> * cio.c: Likewise.
> * cstreams.c: Likewise.
> * env.c: Likewise.
>
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the Swedish team of translators. The file is available at:
http://translationproject.org/latest/gcc/sv.po
(This file, 'gcc-5.1.0.sv.po', has just
> The problem is that ipa_icf::sem_function::parse is lacking the f->init
> call and the function epilog, falling through to the next function that
> happens to follow.
Thank you, that is indeed the devirtualization issue - I suppose the function
descriptors confuses the code even more. I will fi
--- Begin Message ---
gcc/c-family/
2015-03-27 Jan Kratochvil
* c-common.c (c_fully_fold_internal, binary_op_error): Add ATSIGN_EXPR.
* c-lex.c (c_lex_with_flags): Add ATSIGN_EXPR.
gcc/c/
2015-03-27 Jan Kratochvil
* c-parser.c (enum c_parser_prec): Add PREC_ATSIGN.
Hi,
The attached patch tries to fix PR49551.
For following test-case:
int x = 1;
int x;
Passing -O -fdata-sections causes ICE for target arm-linux-gnueabihf.
The bug is latent on trunk, after r221297. Reverting r221297 reproduces ICE.
Before r221297:
ICE was caused in get_variable_section becaus
On Sun, May 31, 2015 at 12:04 AM, Andreas Schwab wrote:
> configure:28726: checking for -fno-PIE option
> configure:28737: g++ -c -g conftest.cpp >&5
> configure:28737: $? = 0
> configure:28745: result: yes
Since GCC is written in C++ now, we need to check CXXFLAGS instead of CFLAGS
for NO_PIE_
The problem is that ipa_icf::sem_function::parse is lacking the f->init
call and the function epilog, falling through to the next function that
happens to follow.
Revision r223897:
Dump of assembler code for function ipa_icf::sem_function::parse(cgraph_node*,
bitmap_obstack*):
0x4194c
Recently I noticed that there are several targets which can't be built
with -Werror enabled during stage 1 build due to C++11 compatibility
warning (whitespace between string literal and macro). Namely, all
mingw32-* and cris-* (except cris-elf) targets.
The attached patch fixes these warnings (I
On Sun, May 31, 2015 at 05:11:52AM +0200, Jan Hubicka wrote:
> @@ -1548,6 +1503,10 @@ eliminate_unnecessary_stmts (void)
>something_changed |= remove_dead_phis (bb);
> }
>
> + if (bb_postorder)
> +free (bb_postorder);
> + bb_postorder = NULL;
Since free (NULL) is a no-op, that
The code here was assuming that get_maxval_strlen returns an INTEGER_CST.
As the testcase demonstrates, that is not always true, so check for that
before calling compare_tree_int. E.g. gimple_fold_builtin_strncpy already
has this check.
Bootstrapped/regtested on x86_64-linux, ok for trunk and 5?
Jan Hubicka writes:
> I am not sure I have access to working ia64 box. Can you possibly help me
> to debug this? Is it devirtualization related?
Here's a backtrace:
0x40422311 in bitmap_obstack_alloc_stat (
bit_obstack=0x4194cf20
) at
../../gcc/bitmap.c:288
288 b
configure:28726: checking for -fno-PIE option
configure:28737: g++ -c -g conftest.cpp >&5
configure:28737: $? = 0
configure:28745: result: yes
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something compl
25 matches
Mail list logo
