Original Message
Subject: [PATCH] Fix handling of context diff patches in mklog
Date: Wed, 22 Jan 2014 18:36:23 +0400
From: Yury Gribov
To: GCC Patches , Diego Novillo
CC: Viacheslav Garbuzov , Yuri Gribov
Hi,
This patch improves support for context diffs in mklog and
-- Forwarded message --
From: Dmitry Gorbachev
Date: Sat, 28 Dec 2013 02:33:18 +0400
Subject: [Patch, trivial] PR 56653: Fix warning when verifying
checksums from MD5SUMS file in tarballs
To: gcc-patches@gcc.gnu.org
This patch is to fix `md5sum: WARNING: 1 line is improperly forma
The old build_cleanup called mark_used; the new one that just calls
cxx_maybe_build_cleanup didn't any more. So let's add a call in the
latter function.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit be2e25f452c30b0a7a00a803422cdbbd80c4e9c3
Author: Jason Merrill
Date: Tue Jan 28 22:3
We already deal with PARM_DECLs that aren't available for lookup in a
late-specified return type, but this case needs the same treatment for a
local variable. During normal instantiation of the lambda we find the
local variable fine, but later when we're doing dump_template_bindings
from cxx_p
On Wed, 29 Jan 2014, Joseph S. Myers wrote:
> It is appropriate for glibc maintainers to seek consensus in the glibc
> community on minimum requirements for glibc ports, just as on any other
> question about what is or is not supported in glibc. For example, it is
> presently expected that a p
On Tue, 28 Jan 2014, David Edelsohn wrote:
> On Tue, Jan 28, 2014 at 4:19 PM, Joseph S. Myers
> wrote:
>
> > The glibc libm testsuite has much more thorough coverage (hopefully soon
> > to include running all tests in all rounding modes by default) than it did
> > two years ago, and it's a pain
On Tue, Jan 28, 2014 at 4:19 PM, Joseph S. Myers
wrote:
> The glibc libm testsuite has much more thorough coverage (hopefully soon
> to include running all tests in all rounding modes by default) than it did
> two years ago, and it's a pain to keep test results clean across all
> architectures wh
On Tue, Jan 28, 2014 at 7:17 PM, Bill Schmidt
wrote:
> David suggested privately that I rework some of the pattern names to fit
> in with existing practice. I've done this, and the result is below.
> Bootstrapped and tested on powerpc64{,le}-unknown-linux-gnu with no
> regressions. Is this ok f
Hi,
David suggested privately that I rework some of the pattern names to fit
in with existing practice. I've done this, and the result is below.
Bootstrapped and tested on powerpc64{,le}-unknown-linux-gnu with no
regressions. Is this ok for trunk?
Thanks,
Bill
On Thu, 2014-01-23 at 18:08 -0600
On Tue, Jan 28, 2014 at 3:42 PM, Gerald Pfeifer wrote:
> On Tue, 28 Jan 2014, H.J. Lu wrote:
>> Here is the patch for changes.html. OK to install?
>
> Yes. Just say "command-line option" please.
>
This is what I checked in.
Thanks.
--
H.J.
---
Index: changes.html
On Tue, 28 Jan 2014, H.J. Lu wrote:
> Here is the patch for changes.html. OK to install?
Yes. Just say "command-line option" please.
Thanks,
Gerald
Hi!
I've started an --enable-checking=valgrind bootstrap during the weekend,
but only on Sunday afternoon and thus killed it on Monday morning, so it
didn't get very far, but still reported a problem where the build tools
had uninitialized memory use in copy_rtx:
case CLOBBER:
/* Share c
I merged GCC trunk revision 207214 to the gccgo branch.
Ian
Hi!
As discussed in the PR and similarly to what has been done previously
for __builtin_setjmp only, this patch attempts to decrease number of
EDGE_ABNORMAL edges in functions with non-local gotos and/or setjmp or
other functions that return twice.
Because, if we have many non-local labels or call
On Tue, Jan 28, 2014 at 01:14:32PM +0100, Richard Biener wrote:
> > I admit I fully don't understand why exactly, but my experimentation so far
> > showed that for read/write and write/read ddrs it is ok and desirable to
> > ignore the dist > 0 && DDR_REVERSED_P (ddr) cases, but for write/write
> >
Committed to dmalcolm/jit:
As discussed in http://gcc.gnu.org/ml/jit/2014-q1/msg1.html,
experiments with adding libgccjit to GNU Octave revealed the absence of
a way for a user of libgccjit to separate one-time startup from
per-invocation activities.
For example, the existing GNU Octave JIT h
In this testcase, we deduce "Bar const" for T and substitute it into the
second parameter, accidentally getting a pointer to const member
function because we forgot to strip the const from Bar.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit 35f0fd76efae307b54f9fa11d39c988699eb4214
Author
This patch to the Go frontend puts nointerface methods in unique
sections. A method marked nointerface may not be needed in the final
link, and putting it in a unique section makes it possible for the
linker to discard it if possible. Bootstrapped and ran Go testsuite on
x86_64-unknown-linux-gnu.
Hi,
On 01/28/2014 10:02 PM, Jason Merrill wrote:
On 01/28/2014 01:33 PM, Paolo Carlini wrote:
Ah! Then I guess that in order to fix c++/58561 only is_base_type needs
tweaking: shall we change the default to just return 0?
Makes sense.
Good. Then I'm finishing testing the below.
Thanks,
Paolo
`On Tue, Jan 28, 2014 at 1:10 PM, Thomas Schwinge
wrote:
>
> OK, I agree to all of that, but I'd assume that if the compiler doesn't
> do such value tracking to see whether all cases have been covered, it
> also souldn't emit such possibly unitialized warning, to not cause false
> positive warning
On Tue, 28 Jan 2014, David Edelsohn wrote:
> Joseph,
>
> Adding the various tests for overflow slows down some other code where
> performance is important. Explicitly changing rounding mode would be
> even more invasive and have significant performance impact.
>
> This long double format never
Hi!
On Tue, 28 Jan 2014 09:12:44 -0800, Ian Lance Taylor wrote:
> On Tue, Jan 28, 2014 at 8:11 AM, Thomas Schwinge
> wrote:
> > On Tue, 28 Jan 2014 06:52:30 -0800, Ian Lance Taylor
> > wrote:
> >> On Tue, Jan 28, 2014 at 6:36 AM, Thomas Schwinge
> >> wrote:
> >> > Avoid "'dc' may be uninitial
On 01/28/2014 01:33 PM, Paolo Carlini wrote:
Ah! Then I guess that in order to fix c++/58561 only is_base_type needs
tweaking: shall we change the default to just return 0?
Makes sense.
Jason
When we're building up the constructor for the anonymous union type,
build_anon_member_initialization was getting confused, assuming that
anything it found with anonymous union type would be a COMPONENT_REF.
But within the constructor, *this also has anonymous union type.
Tested x86_64-pc-linu
On Tue, Jan 28, 2014 at 12:51 PM, Joseph S. Myers
wrote:
> On Mon, 6 Jan 2014, David Edelsohn wrote:
>
>> On Sat, Jan 4, 2014 at 8:16 AM, Joseph S. Myers
>> wrote:
>> > This patch fixes various cases of spurious overflow exceptions in the
>> > IBM long double support code. The generic issue is
This ICE was introduced when I adjusted lookup_and_check_tag to find
template template parameters so that they can be friends. But in this
case that meant we started to try to define the ttp as a class, leading
to chaos. In lookup_and_check_tag we can tell that we're in a class
definition by
On Tue, Jan 28, 2014 at 5:23 AM, Dodji Seketeli wrote:
> Dodji Seketeli writes:
>
>> Here is the patch I am committing right now.
>>
>> gcc/ChangeLog
>>
>> * input.c (location_get_source_line): Bail out on when line number
>> is zero, and test the return value of
>> lookup_or_ad
... by the way, I don't understand why we are appending the constructor
at all for the unnamed bit-field?!? Eg, what about the below?
Thanks,
Paolo.
Index: cp/typeck2.c
===
--- cp/typeck2.c(revision 207
On 01/28/2014 06:05 PM, Jason Merrill wrote:
My earlier work to support return type deduction omitted support for
debugging information; this patch fixes that oversight. It also
corrects the mangled name of 'operator auto', which should reflect the
'auto' rather than the deduced return type.
My earlier work to support return type deduction omitted support for
debugging information; this patch fixes that oversight. It also
corrects the mangled name of 'operator auto', which should reflect the
'auto' rather than the deduced return type.
Tested x86_64-pc-linux-gnu, applying to trunk
On Mon, 6 Jan 2014, David Edelsohn wrote:
> On Sat, Jan 4, 2014 at 8:16 AM, Joseph S. Myers
> wrote:
> > This patch fixes various cases of spurious overflow exceptions in the
> > IBM long double support code. The generic issue is that an initial
> > approximation is computed by using the releva
> Hi,
>
> On Tue, 28 Jan 2014, Richard Biener wrote:
>
> > >> The EH optimizations involving cleanups with only clobbers in them
> > >> are that if at the end of the cleanup after only CLOBBER stmts you
> > >> would rethrow the exception externally, then the clobber isn't needed
> > >> and the
On Tue, Jan 28, 2014 at 8:11 AM, Thomas Schwinge
wrote:
> On Tue, 28 Jan 2014 06:52:30 -0800, Ian Lance Taylor wrote:
>> On Tue, Jan 28, 2014 at 6:36 AM, Thomas Schwinge
>> wrote:
>> > Avoid "'dc' may be uninitialized" warning.
>> >
>> > libiberty/
>> > * cp-demangle.c (d_demangl
On Tue, Jan 28, 2014 at 8:42 AM, Uros Bizjak wrote:
> On Tue, Jan 28, 2014 at 5:35 PM, H.J. Lu wrote:
>
> The .code16gcc directive was added to binutils back in 1999:
>
>> scan-asm testcase doesn't do anything useful. The only
>> difference in assembly code between -m16 and -m32 is the
>> .c
It occurred to me that we don't need to call merge_types at all if we're
just going to throw away the result.
commit 00a4445cf80b647d14144c9b509cf06d052a888e
Author: Jason Merrill
Date: Tue Jan 28 08:50:23 2014 -0500
* decl.c (duplicate_decls): Tweak.
diff --git a/gcc/cp/decl.c b/gcc/c
On Tue, Jan 28, 2014 at 08:35:13AM -0800, H.J. Lu wrote:
> Here is a run-time test. It builds 16-bit image for BIOS and
> loads it into qemu-system-i386. OK to install?
Ugh, I'd say we don't want this kind of stuff in gcc testsuite.
A scan-assembler would be IMHO enough.
> PR target/59672
> * g
> -Original Message-
> From: Iyer, Balaji V
> Sent: Monday, January 27, 2014 4:36 PM
> To: Jakub Jelinek
> Cc: Jason Merrill; 'Jeff Law'; 'Aldy Hernandez'; 'gcc-patches@gcc.gnu.org';
> 'r...@redhat.com'
> Subject: RE: [PING] [PATCH] _Cilk_for for C and C++
>
> > -Original Message
On Tue, Jan 28, 2014 at 5:01 PM, Uros Bizjak wrote:
> On Mon, Jan 27, 2014 at 8:44 PM, H.J. Lu wrote:
>
>> The .code16gcc directive was added to binutils back in 1999:
>>
>> ---
>>'.code16gcc' provides experimental support for generating 16-bit code
>> from gcc, and differs from '.code16' in
On Tue, Jan 28, 2014 at 8:01 AM, Uros Bizjak wrote:
> On Mon, Jan 27, 2014 at 8:44 PM, H.J. Lu wrote:
>
>> The .code16gcc directive was added to binutils back in 1999:
>>
>> ---
>>'.code16gcc' provides experimental support for generating 16-bit code
>> from gcc, and differs from '.code16' in
On Tue, Jan 28, 2014 at 5:35 PM, H.J. Lu wrote:
The .code16gcc directive was added to binutils back in 1999:
> scan-asm testcase doesn't do anything useful. The only
> difference in assembly code between -m16 and -m32 is the
> .code16gcc directive All magic is done in assembler.
The test
On Tue, Jan 28, 2014 at 8:30 AM, Uros Bizjak wrote:
> On Tue, Jan 28, 2014 at 5:01 PM, Uros Bizjak wrote:
>> On Mon, Jan 27, 2014 at 8:44 PM, H.J. Lu wrote:
>>
>>> The .code16gcc directive was added to binutils back in 1999:
>>>
>>> ---
>>>'.code16gcc' provides experimental support for gener
On 28/01/14 14:16, kazu_hir...@mentor.com wrote:
> Hi,
>
> Attached is a patch to fix gcc.target/arm/thumb-cbranchqi.c.
>
> Without this patch, the testcase fails because these days gcc
> generates:
>
> ldrb:
> ldrbr3, [r0, #8]
> mov r0, #2
> cmp r3, #127
>
Hi!
On Tue, 28 Jan 2014 06:52:30 -0800, Ian Lance Taylor wrote:
> On Tue, Jan 28, 2014 at 6:36 AM, Thomas Schwinge
> wrote:
> > Avoid "'dc' may be uninitialized" warning.
> >
> > libiberty/
> > * cp-demangle.c (d_demangle_callback): Put __builtin_unreachable
> > in place,
On Mon, Jan 27, 2014 at 8:44 PM, H.J. Lu wrote:
> The .code16gcc directive was added to binutils back in 1999:
>
> ---
>'.code16gcc' provides experimental support for generating 16-bit code
> from gcc, and differs from '.code16' in that 'call', 'ret', 'enter',
> 'leave', 'push', 'pop', 'pusha
I checked vectorization code, it seems that only relevant place
vec_widen_mult_even/odd & vec_widen_mult_lo/hi are generated is in
supportable_widening_operation. One of these pairs is selected, with priority
given to vec_widen_mult_even/odd if it is a reduction loop. However, lo/hi pair
seems
On Tue, Jan 28, 2014 at 6:36 AM, Thomas Schwinge
wrote:
> Avoid "'dc' may be uninitialized" warning.
>
> libiberty/
> * cp-demangle.c (d_demangle_callback): Put __builtin_unreachable
> in place, to help the compiler.
>
> --- libiberty/cp-demangle.c
> +++ libiberty/cp-demang
This implements simple pattern matching for folding of
pointer subtraction GIMPLE IL which is performed in an
integer type. It handles the simple case, like the
others in associate_plusminus (cases involving cancellation).
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
Richard.
Hi!
This got committed to trunk as r206477; one small nit:
On Tue, 10 Dec 2013 12:38:34 +0100, Jakub Jelinek wrote:
> * libbacktrace/Makefile.am (libsanitizer_libbacktrace_la_SOURCES): Add
> ../../libiberty/cp-demangle.c.
Trying to build trunk r207180 with C*FLAGS='-Og -ggdb', a com
Hi all,
I've committed the attached trivial patch to remove a useless statement as
r207193.
Thanks,
Kyrill
2014-01-28 Kyrylo Tkachov
* config/arm/arm.c (arm_new_rtx_costs): Remove useless statement
at const_int_cost.diff --git a/gcc/config/arm/arm.c b/gcc/config/arm/arm.c
index bf
Hi,
Attached is a patch to fix gcc.target/arm/thumb-cbranchqi.c.
Without this patch, the testcase fails because these days gcc
generates:
ldrb:
ldrbr3, [r0, #8]
mov r0, #2
cmp r3, #127
bls .L2
mov r0, #5
.L2:
@ sp needed
Hi,
On Tue, 28 Jan 2014, Jakub Jelinek wrote:
> On Tue, Jan 28, 2014 at 01:48:21PM +0100, Michael Matz wrote:
> > Hi,
> >
> > On Tue, 28 Jan 2014, Jakub Jelinek wrote:
> >
> > > There are two kinds of clobbers, the direct ones, which surely can be
> > > safely removed by ehcleanup1 if they are
Hi Bernd,
2014/1/27 Bernd Schmidt :
> Once I worked around this by unsetting the environment variables around this
> compiler invocation here, the next problem is exposed - the code tries to
> link together files compiled for the target (created by the code quoted
> above) and the host (the _omp_d
On Tue, 28 Jan 2014, Andreas Schwab wrote:
> Hans-Peter Nilsson writes:
>
> > See is_release in that same configure.ac, that might be the only
> > additional condition that's needed.
>
> is_release only distinguishes a release from a snapshot, but does not
> say anything whether its a tarball or a
Hans-Peter Nilsson writes:
> See is_release in that same configure.ac, that might be the only
> additional condition that's needed.
is_release only distinguishes a release from a snapshot, but does not
say anything whether its a tarball or a VC checkout (ie. is_release=yes
is also possible in a
On Mon, Jan 20, 2014 at 10:50 AM, Richard Biener wrote:
>
> This improves var-tracking dataflow convergence by using post order
> on the inverted CFG - which is appropriate for forward dataflow
> problems. This haves compile-time spent in var-tracking for PR45364
> (it also improves other testcas
Dodji Seketeli writes:
> Here is the patch I am committing right now.
>
> gcc/ChangeLog
>
> * input.c (location_get_source_line): Bail out on when line number
> is zero, and test the return value of
> lookup_or_add_file_to_cache_tab.
>
> gcc/testsuite/ChangeLog
>
> * c-c++
Here is the patch I am committing right now.
gcc/ChangeLog
* input.c (location_get_source_line): Bail out on when line number
is zero, and test the return value of
lookup_or_add_file_to_cache_tab.
gcc/testsuite/ChangeLog
* c-c++-common/cpp/warning-zero-location.c
On Tue, Jan 28, 2014 at 01:48:21PM +0100, Michael Matz wrote:
> Hi,
>
> On Tue, 28 Jan 2014, Jakub Jelinek wrote:
>
> > There are two kinds of clobbers, the direct ones, which surely can be
> > safely removed by ehcleanup1 if they are the only reason why there is a
> > landing pad which will be
Adding gcc-patches.
Hi Bernd,
The table is used in libgomp (see my patch [1]), as proposed by Jakub
(see [2]). The idea is that the order of entries in the host and
target tables must be identical. This allows to set up one-to-one
correspondence between host and target addresses.
In my patch l
On Tue, Jan 28, 2014 at 3:25 AM, Hans-Peter Nilsson wrote:
> On Mon, 27 Jan 2014, Richard Biener wrote:
>> >Huh, so we have C for cross-builds and C++ for bootstraps.
>>
>> No, we use a C host compiler in both cases. Only stages 2 and 3 build with a
>> C++ compiler.
>
> Tomatos potatoes! As fort
Hi,
On Tue, 28 Jan 2014, Jakub Jelinek wrote:
> There are two kinds of clobbers, the direct ones, which surely can be
> safely removed by ehcleanup1 if they are the only reason why there is a
> landing pad which will be rethrown outside of the current function,
You can only safely (as in, not
Committed as they are also wrong (no handling of DDR_REVERSED_P).
Richard.
2014-01-28 Richard Biener
* tree-data-ref.h (ddr_is_anti_dependent, ddrs_have_anti_deps):
Remove.
Index: gcc/tree-data-ref.h
===
*** gcc
On Tue, 28 Jan 2014 12:09:27 +
Ramana Radhakrishnan wrote:
> On Thu, Jan 23, 2014 at 3:16 PM, Yury Gribov
> wrote:
> > Hi,
> >
> > Julian Brown has proposed patch
> > (http://gcc.gnu.org/ml/gcc-patches/2013-06/msg01191.html) for the
> > dreadful push_minipool_fix error
> > (http://gcc.gnu.or
Hi,
On Tue, 28 Jan 2014, Richard Biener wrote:
> >> The EH optimizations involving cleanups with only clobbers in them
> >> are that if at the end of the cleanup after only CLOBBER stmts you
> >> would rethrow the exception externally, then the clobber isn't needed
> >> and the whole cleanup c
On Fri, 24 Jan 2014, Jakub Jelinek wrote:
> Hi!
>
> I admit I fully don't understand why exactly, but my experimentation so far
> showed that for read/write and write/read ddrs it is ok and desirable to
> ignore the dist > 0 && DDR_REVERSED_P (ddr) cases, but for write/write
> ddrs it is undesira
On Fri, Dec 20, 2013 at 6:50 PM, Renlin Li wrote:
> Hi all,
>
> This patch will add armv7ve support to gcc. Armv7ve is basically a armv7-a
> architecture profile with Virtualization Extensions. Additional test cases
> are also added.
>
> With this patch and to keep backward compatibility with old
On Fri, Jan 24, 2014 at 5:16 PM, Ian Bolton wrote:
> Hi there!
>
> An existing optimisation for Thumb-2 converts t32 encodings to
> t16 encodings to reduce codesize, at the expense of causing
> redundant flag setting for ADD, AND, etc. This redundant flag
> setting can have negative performance i
On Thu, Jan 23, 2014 at 3:16 PM, Yury Gribov wrote:
> Hi,
>
> Julian Brown has proposed patch
> (http://gcc.gnu.org/ml/gcc-patches/2013-06/msg01191.html) for the dreadful
> push_minipool_fix error (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49423)
> in June but it didn't seem to get enough attent
On Tue, Jan 28, 2014 at 11:48:16AM +0100, Richard Biener wrote:
> On Mon, Jan 20, 2014 at 5:22 PM, Jan Hubicka wrote:
> >>
> >> Yes. Say, this could be surrounded by some try/catch, if we do it the
> >> first
> >> way, a would be still considered live across the EH path to whatever
> >> catches
Committed to branch dmalcolm/jit:
gcc/testsuite/
* jit.dg/harness.h (test_jit): Move the various calls to set up
options on the context into...
(set_options): ...this new function.
---
gcc/testsuite/ChangeLog.jit| 6 ++
gcc/testsuite/jit.dg/harness.h | 23
On 12/17/2013 12:39 PM, Michael V. Zolotukhin wrote:
Here is a patch 2/3: Add tables generation.
This patch is just a slightly modified patch sent a couple of weeks ago. When
compiling with '-fopenmp' compiler generates a special symbol, containing
addresses and sizes of globals/omp_fn-function
On Mon, Jan 20, 2014 at 5:22 PM, Jan Hubicka wrote:
>>
>> Yes. Say, this could be surrounded by some try/catch, if we do it the first
>> way, a would be still considered live across the EH path to whatever catches
>> it.
>>
>> The EH optimizations involving cleanups with only clobbers in them are
This adds new (non-public) constructors to shared_ptr and
__shared_count so that weak_ptr::lock() can be implemented without
exceptions. This allows it to be used with -fno-exceptions and also
avoids the overhead of throwing and catching an exception when the
weak_ptr has expired.
Tested x86_64-l
On Tue, Jan 28, 2014 at 10:40:51AM +0100, Richard Biener wrote:
> The patch doesn't make much sense to me. I think the problem is that
> NAMELIST_DECL is output in a ref section (LTO_namelist_decl_ref) but
> the output routine writes other refs (via stream_write_tree and
> outputting the construct
Hi!
On Tue, 14 Jan 2014 07:09:33 -0800, I wrote:
> Here is a patch series that adds initial support for OpenACC data
> clauses. It is not yet complete, but I thought I might as well already
> now strive to get this integrated upstream instead of "hoarding" the
> patches locally.
Committed to gom
On Tue, 21 Jan 2014, Aldy Hernandez wrote:
> Hi folks.
>
> The problem here is that while streaming the DECL_NAME with stream_read_tree()
> and consequently lto_output_tree(), we trigger an ICE because we are recursing
> on the DFS walk:
>
> else
> {
> /* This is the first time we se
76 matches
Mail list logo
