OK.
Jason
On Tue, 26 Apr 2016, Bernd Edlinger wrote:
For instance PR libstdc++/69881: gmp.h did this:
#define __need_size_t /* tell gcc stddef.h we only want size_t */
#include /* for size_t */
I've persuaded Jonathan to work around that in libstdc++.
Of course the in-tree build does work with le
On 04/26/2016 08:35 PM, H.J. Lu wrote:
This
/* { dg-final { scan-assembler-times "vmovdqa64\[
\\t\]+\[^\{\n\]*%ymm\[0-9\]+\[^\nxy\]*\\(.{5}(?:\n|\[ \\t\]+#)" 1 {
target nonpic } } } */
fails on x32 since x32 with 32-bit pointers has (%r10d) instead of
(%r10). .{5} doesn't match.
What is this
On Tue, Apr 26, 2016 at 12:32 PM, Bernd Schmidt wrote:
> On 04/26/2016 08:35 PM, H.J. Lu wrote:
>>
>> This
>>
>> /* { dg-final { scan-assembler-times "vmovdqa64\[
>> \\t\]+\[^\{\n\]*%ymm\[0-9\]+\[^\nxy\]*\\(.{5}(?:\n|\[ \\t\]+#)" 1 {
>> target nonpic } } } */
>>
>> fails on x32 since x32 with 32-b
On Tue, Apr 26, 2016 at 11:42 AM, H.J. Lu wrote:
> On Tue, Apr 26, 2016 at 9:33 AM, H.J. Lu wrote:
>> On Tue, Apr 26, 2016 at 9:27 AM, Ilya Enkovich
>> wrote:
>>> 2016-04-26 19:20 GMT+03:00 Ilya Enkovich :
2016-04-26 19:12 GMT+03:00 H.J. Lu :
> On Tue, Apr 26, 2016 at 9:07 AM, Ilya Enk
On Tue, 26 Apr 2016, Bernd Edlinger wrote:
> Hi,
>
> as we all know, it's high time now to adjust the minimum supported
> gmp/mpfr/mpc versions for gcc-7.
I think updating the minimum versions (when using previously built
libraries, not in-tree) is only appropriate when it allows some cleanup i
On 03/26/2016 05:56 AM, Jake Hamby wrote:
On Mar 23, 2016, at 05:56, Christos Zoulas
wrote:
In article , Jake
Hamby wrote:
Hi,
Thanks a lot for your patch. I applied it to our gcc-5 in the
tree. Unfortunately gcc-5 seems that it was never tested to even
compile. I fixed the simple compilati
On Tue, 26 Apr 2016, Richard Biener wrote:
On Sun, Apr 24, 2016 at 7:14 PM, Marc Glisse wrote:
Hello,
trying to move a first pattern from fold_comparison.
I first tried without single_use. It brought the number of 'free' in
g++.dg/tree-ssa/pr61034.C down to 11, changed gcc.dg/sms-6.c to only
On 03/31/2016 02:29 PM, Jake Hamby wrote:
The failures all seem to be related to trying to read a value from an
array of 64-bit values and loading it into a 32-bit register. It
seems like there should be a special insn defined for this sort of
array access, since VAX has mova* and pusha* variant
On 04/01/2016 01:06 PM, Jake Hamby wrote:
My theory is that it has to do with liveness detection and a write
into the stack frame being incorrectly seen as updating a local
variable, but that could be completely wrong. I was hoping that by
cc'ing gcc-patches that somebody more familiar with why
On 03/26/2016 08:38 AM, Jake Hamby wrote:
Unfortunately, my previous patch that included a change to gcc/config/vax/vax.h
that increased FIRST_PSEUDO_REGISTER from 16 to 17 breaks the C++ exception
handling that I’d worked so hard to get right with the rest of the patch. I
believe I need to de
On 26 April 2016 at 16:31, Richard Biener wrote:
> On Mon, 25 Apr 2016, Prathamesh Kulkarni wrote:
>
>> On 6 April 2016 at 14:54, Richard Biener wrote:
>> > On Wed, 6 Apr 2016, Richard Biener wrote:
>> >
>> >> On Wed, 6 Apr 2016, Prathamesh Kulkarni wrote:
>> >>
>> >> > On 6 April 2016 at 13:44,
On 04/26/2016 08:04 AM, Rainer Orth wrote:
When working on a couple of Cilk Plus issues lately (PRs target/60290,
target/68945), I noticed that you have to modify the libcilkplus sources
to enable various debugging output. This seems silly, and the following
patch allows defining them from the c
On 04/11/2016 08:10 PM, Vladimir Makarov wrote:
On 04/10/2016 11:24 PM, Zhouyi Zhou wrote:
save a function call to init_reload when using lra, also remove the a
type error in reload1.c
because init_reload is called only once when compile process, the
performance reduction may not be significant
On 04/04/2016 06:00 AM, Senthil Kumar Selvaraj wrote:
2016-04-04 Senthil Kumar Selvaraj
* gcc.c-torture/compile/pr69102.c: Require scheduling support.
* gcc.c-torture/compile/pr37669.c: Require >=32 bit integers.
* gcc.c-torture/execute/bitfld-6.c: Likewise.
* gcc.c-torture/ex
On 01/31/2016 03:16 PM, Alan Modra wrote:
The comment says this test is supposed to prevent "a narrower
operation than requested", but it actually only allows a larger
subreg, not one the same size. Fix that.
Bootstrapped and regression tested powerpc64-linux. OK for stage1?
Note that this bu
This patch by Chris Manghane adds Enclosed_var_expression to the Go
frontend. This represents a reference from a function literal to a
variable defined in the enclosing function. This simplifies the
existing code, and provides a base for future work. Bootstrapped and
ran Go testsuite on x86_64-p
On 04/25/2016 03:07 AM, Bernd Schmidt wrote:
On 04/22/2016 03:57 PM, Jason Merrill wrote:
This looks good, but can we move the code into c-common rather than
duplicate it?
That would be this patch. Also passes testing on x86_64-linux.
Hi Bernd,
I like the idea behind the patch! So much so
Hi Bernd,
On 16-04-25 12:15:50, Bernd Schmidt wrote:
> On 04/18/2016 02:26 PM, Dhole wrote:
> >A few months ago I submited a patch to allow the embedded timestamps by
> >C/C++ macros to be set externally [2], which was already an improvement
> >over [1]. I was told to wait until the GCC 7 stage 1
On 12/15/2015 10:25 AM, Kyrill Tkachov wrote:
Hi all,
This converts the preprocessor check for WORD_REGISTER_OPERATIONS into a
runtime one
in rtlanal.c.
Since this one was in combination with an "#if defined" and used to
guard an if-statement
I'd appreciate it if someone gave it a double-check
On 02/17/2016 07:24 AM, Nick Clifton wrote:
Hi Guys,
Redefining a previously defined static function as both public and
weak triggers an ICE in ipa-visibility.c:
internal compiler error: in function_and_variable_visibility, at
ipa-visibility.c:518
This bug has been discussed and patch p
Hi. I've been working on Rust support for gdb, and I needed this patch
as a prerequisite.
DW_LANG_Rust is only defined in DWARF 5, which isn't released yet.
However, the value is mentioned in the DWARF issue requesting the
addition; and similar DWARF-5-only constants have already been added to
dw
On 04/26/2016 09:39 PM, H.J. Lu wrote:
make check-gcc RUNTESTFLAGS="--target_board='unix{-mx32}'
i386.exp=avx512vl-vmovdqa64-1.c"
Unfortunately, that doesn't work:
/usr/include/gnu/stubs.h:13:28: fatal error: gnu/stubs-x32.h: No such
file or directory
compilation terminated.
Trying to follo
On Tue, Apr 26, 2016 at 03:02:38PM +0200, Jakub Jelinek wrote:
> The debugging hack is too ugly and slows down the compiler (by artificially
> increasing number of collisions), so it is not appropriate, but perhaps we
> can add some internal only use OEP_* flag, pass it to the recursive calls
> of
On Tue, Apr 26, 2016 at 03:02:38PM +0200, Jakub Jelinek wrote:
> I've been using the attached hack; without this patch during x86_64-linux
> and i686-linux yes,extra,rtl checking bootstraps there were 66931
> notes (surprisingly only from the ivopts and gimple-ssa-strength-reduction
> hash tables,
On 04/26/2016 11:28 PM, Dhole wrote:
I've fixed all the spaces issues. I've also changed the "unsigned long long"
to "time_t" as you suggested. Also, to improve reliability I'm now
using strtoll rather than strtoull, so that negative values can be
detected in SOURCE_DATE_EPOCH, which are treate
PR c++/66639 asked to declare __func__ , __FUNCTION__ and
__PRETTY_FUNCTION__ as constexpr. With the request fulfilled
sometime in the 6.0 time frame (possibly as a result of fixing
c++/70353), the attached patch implements the corresponding
change suggested in c++/66561 - __builtin_LINE at al.
On Tue, Apr 26, 2016 at 3:11 PM, Bernd Schmidt wrote:
> On 04/26/2016 09:39 PM, H.J. Lu wrote:
>>
>> make check-gcc RUNTESTFLAGS="--target_board='unix{-mx32}'
>> i386.exp=avx512vl-vmovdqa64-1.c"
>
>
> Unfortunately, that doesn't work:
>
> /usr/include/gnu/stubs.h:13:28: fatal error: gnu/stubs-x32.
On Tue, Apr 26, 2016 at 09:03:03AM -0600, Jeff Law wrote:
> On 04/26/2016 07:08 AM, Jakub Jelinek wrote:
> >Hi!
> >
> >I've noticed a warning during bootstrap:
> >../../gcc/reorg.c: In function ‘void try_merge_delay_insns(rtx_insn*,
> >rtx_insn*)’:
> >../../gcc/reorg.c:1431:12: warning: name looku
On 27/04/16 00:14, Richard Biener wrote:
On Fri, Apr 15, 2016 at 12:44 PM, kugan
wrote:
As pointed out by Richard, for signed & sign-bit-CST value range should be
[-INF, 0] range, not a [-INF, INF] range as happens now.
This patch fixes this. I bootstrapped and regression tested for
x86-64-l
On Mon, Apr 25, 2016 at 04:25:27PM +0200, Bernd Schmidt wrote:
> On 04/25/2016 04:21 PM, Bernd Schmidt wrote:
> >On 04/25/2016 03:30 PM, Trevor Saunders wrote:
> >>On Mon, Apr 25, 2016 at 02:28:51PM +0200, Bernd Schmidt wrote:
> >>>On 04/20/2016 08:22 AM, tbsaunde+...@tbsaunde.org wrote:
> From
On 03/02/2016 02:53 PM, Vladimir Makarov wrote:
The overall effect of this patch seems to be fairly minimal in
practice, which is slightly disappointing. On the whole, it seems to
be a very slight net positive, with few instances where we generate
additional instructions.
I am just speculating
On 04/25/2016 03:11 AM, Bernd Schmidt wrote:
On 03/02/2016 10:53 PM, Vladimir Makarov wrote:
The patch is ok for me. But I'd wait for GCC7. People are sensitive to
their code performance degradation. Even in most cases the patch
improves performance, in some case it can worsen code and peop
On 04/24/2016 11:40 PM, Sebastian Huber wrote:
Ok, what about the GCC trunk?
On 20/04/16 14:35, Sebastian Huber wrote:
Hello,
I know that I am pretty late, but is there a chance to get this into
the GCC 6.1 release?
On 19/04/16 14:56, Sebastian Huber wrote:
v2: Do not use architecture config
On 03/15/2016 08:18 AM, Andreas Schwab wrote:
Like x32, aarch64 ILP32 needs to define FFI_SIZEOF_JAVA_RAW. This fixes
the java interpreter.
Andreas.
* src/aarch64/ffitarget.h (FFI_SIZEOF_JAVA_RAW) [__ILP32__]:
Define.
Doesn't libffi come from an upstream project? If so, should
On 03/15/2016 08:46 AM, Andreas Schwab wrote:
* include/private/gcconfig.h [AARCH64] (ALIGNMENT, CPP_WORDSZ):
Define for __ILP32__.
---
boehm-gc/include/private/gcconfig.h | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
Similarly, this should be going to upstream
On 04/26/2016 04:05 PM, Tom Tromey wrote:
Hi. I've been working on Rust support for gdb, and I needed this patch
as a prerequisite.
DW_LANG_Rust is only defined in DWARF 5, which isn't released yet.
However, the value is mentioned in the DWARF issue requesting the
addition; and similar DWARF-5-
Here is the current patch (passed regtest), after moving defer/undefer
from forwprop to fold_stmt_1. I am not sure if checking no_warning at the
end of fold_stmt_1 is safe, or if I should save its value at the beginning
of the function, in case some of the transformations clear it.
On Tue, 26
101 - 138 of 138 matches
Mail list logo
