On Thu, Mar 1, 2012 at 9:23 PM, Bernd Schmidt wrote:
> In pointer_diff we still expect pointer addition to use PLUS_EXPR. I
> discovered this while working on a new port with somewhat unusual
> pointer types.
>
> Interestingly, the C++ frontend also has a pointer_diff function, but
> doesn't seem
There is a 4.5 to 4.7 regression for those (vendor) intrinsic
procedures, which can exists as both subroutine and as function. Example:
INTRINSIC :: etime
CALL etime(tarray, result)
Here, the "etime" gets marked as attr.subroutine, but later in
resolve_intrinsics, it is mapped to the i
On Fri, Mar 2, 2012 at 6:09 AM, Maxim Kuvyrkov wrote:
> On 1/03/2012, at 11:42 PM, Richard Guenther wrote:
>> On Thu, Mar 1, 2012 at 6:28 AM, Maxim Kuvyrkov
>> wrote:
>>> This patch disables graphite loop flattening optimization due to it being
>>> effectively unmaintained. To avoid users tryi
This patch organizes the target-specific changes section alphabetically
(which it nearly was).
Committed as obvious.
R.Index: changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.7/changes.html,v
retrieving revision 1.93
diff -u
Ian Lance Taylor writes:
> This patch to libgo fills out the syscall package for GNU/Linux to match
> all the functions in the syscall package in the master Go library.
> There is a test case for this patch at
> http://code.google.com/p/go/issues/detail?id=3071 . Bootstrapped and
> ran Go testsu
OK for trunk with RM agreement. Obviously, 4.5 & 4.6 are OK too.
Thanks
Paul
On Fri, Mar 2, 2012 at 10:35 AM, Tobias Burnus wrote:
> There is a 4.5 to 4.7 regression for those (vendor) intrinsic procedures,
> which can exists as both subroutine and as function. Example:
>
> INTRINSIC :: eti
On Fri, Mar 2, 2012 at 11:12 AM, Paul Richard Thomas
wrote:
> OK for trunk with RM agreement. Obviously, 4.5 & 4.6 are OK too.
Ok for trunk.
Richard.
> Thanks
>
> Paul
>
> On Fri, Mar 2, 2012 at 10:35 AM, Tobias Burnus wrote:
>> There is a 4.5 to 4.7 regression for those (vendor) intrinsic pr
The GCC 4.7 branch has been created and a first release candidate
is being prepared right now. The branch is closed for now.
Previous Report
===
http://gcc.gnu.org/ml/gcc/2012-02/msg00441.html
The next report will announce the release candidate.
On 03/02/2012 12:15 PM, Richard Guenther wrote:
The GCC 4.7 branch has been created and a first release candidate
is being prepared right now. The branch is closed for now.
Just be clear (I think the information could be useful in general):
mainline can be already considered open for Stage 1 co
Status
==
The trunk has branched for the GCC 4.7 release and is now open
again for general development, stage 1. Please consider not
disrupting it too much during the RC phase of GCC 4.7 so it
is possible to test important fixes for 4.7.0 on it.
Quality Data
Priority
TYPE(*) is Fortran's equivalent to C's "void *buffer". It may only be
used for dummy arguments and essentially might only either be passed on,
or appear in PRESENT, LBOUND/UBOUND/SHAPE/SIZE/IS_CONTIGUOUS - and most
useful: in C_LOC.
Note: For scalar TYPE(*) and for assumed-size dummies, only
This patch documents some more of the changes that have occurred on ARM
this year. I've also re-worded a couple of the existing changes
recorded there to try and improve the clarity to users.
OK?
Index: changes.html
===
RCS file: /cv
On 01/03/12 21:57 , Doug Kwan wrote:
Hi Diego,
This is a backport from trunk to fix a problem in validate_failures.py
when testing a cross compiler.
-Doug
2012-03-01 Doug Kwan
Backport r184357 from trunk
2012-02-17 Doug Kwan
* contrib/testsuite-manage
On Thu, Feb 16, 2012 at 2:17 PM, William J. Schmidt
wrote:
> Greetings,
>
> Given the recent discussion on getting 4.6 cleaned up, I thought I'd
> check back on this one. Thanks!
Ok.
Thanks,
Richard.
> Bill
>
> On Fri, 2012-02-10 at 14:58 -0600, William J. Schmidt wrote:
>> This patch backport
As mentioned on #gcc, the git mirror should also include new major releases.
Diego also documented it on the wiki:
http://gcc.gnu.org/wiki/GitMirror#Adding_a_branch_to_origin.2BAC8.2A
(Wiki page rev. 94 -> 96)
OK for committal?
Tobias
Index: releasing.html
==
Hi,
PR testsuite/16464 notes that some g77/*.f that contain loops were not
compiled with loop flags.
Compiling only testcases with loop optimization that contain
"endfor/enddo" will lead to ~25% fewer tests (some 3 instead of
previously 4).
Testing in progess, ok if this completes success
On Fri, Mar 02, 2012 at 03:00:12PM +0100, Tobias Burnus wrote:
> As mentioned on #gcc, the git mirror should also include new major releases.
>
> Diego also documented it on the wiki:
> http://gcc.gnu.org/wiki/GitMirror#Adding_a_branch_to_origin.2BAC8.2A
> (Wiki page rev. 94 -> 96)
>
> OK for com
On Fri, Mar 2, 2012 at 3:00 PM, Tobias Burnus wrote:
> As mentioned on #gcc, the git mirror should also include new major releases.
>
> Diego also documented it on the wiki:
> http://gcc.gnu.org/wiki/GitMirror#Adding_a_branch_to_origin.2BAC8.2A (Wiki
> page rev. 94 -> 96)
>
> OK for committal?
O
On Fri, Mar 02, 2012 at 03:01:31PM +0100, Bernhard Reutner-Fischer wrote:
> PR testsuite/16464 notes that some g77/*.f that contain loops were not
> compiled with loop flags.
> Compiling only testcases with loop optimization that contain
> "endfor/enddo" will lead to ~25% fewer tests (some 3 in
On Fri, Mar 2, 2012 at 3:05 PM, Jakub Jelinek wrote:
> On Fri, Mar 02, 2012 at 03:01:31PM +0100, Bernhard Reutner-Fischer wrote:
>> PR testsuite/16464 notes that some g77/*.f that contain loops were not
>> compiled with loop flags.
>> Compiling only testcases with loop optimization that contain
>>
On Fri, Mar 2, 2012 at 3:02 PM, Jakub Jelinek wrote:
> On Fri, Mar 02, 2012 at 03:00:12PM +0100, Tobias Burnus wrote:
>> As mentioned on #gcc, the git mirror should also include new major releases.
>>
>> Diego also documented it on the wiki:
>> http://gcc.gnu.org/wiki/GitMirror#Adding_a_branch_to_
On 03/02/2012 03:02 PM, Jakub Jelinek wrote:
releasing.html is wrong for this, it has nothing to do with releasing,
but with branching, so something like that should go into
branching.html instead. From this isn't clear where this command needs
to be run, btw, on gcc.gnu.org directly, somewhere
On Fri, Mar 2, 2012 at 3:25 PM, Bernhard Reutner-Fischer
wrote:
> On Mar 2, 2012 3:09 PM, "Richard Guenther"
> wrote:
>>
>> On Fri, Mar 2, 2012 at 3:05 PM, Jakub Jelinek wrote:
>> > On Fri, Mar 02, 2012 at 03:01:31PM +0100, Bernhard Reutner-Fischer
>> > wrote:
>> >> PR testsuite/16464 notes that
On Fri, Mar 2, 2012 at 3:10 PM, Tobias Burnus wrote:
> On 03/02/2012 03:02 PM, Jakub Jelinek wrote:
>>
>> releasing.html is wrong for this, it has nothing to do with releasing, but
>> with branching, so something like that should go into branching.html
>> instead. From this isn't clear where this
On Thu, 1 Mar 2012, Richard Guenther wrote:
> On Wed, 29 Feb 2012, Richard Guenther wrote:
>
> > On Wed, 29 Feb 2012, Michael Matz wrote:
> >
> > > Hi,
> > >
> > > On Wed, 29 Feb 2012, Richard Guenther wrote:
> > >
> > > > the whole base object - instead I mark the base MEM_REF of such
> > >
Ping^3. Better support for nested if-then-else structures:
> http://gcc.gnu.org/ml/gcc-patches/2011-09/msg01935.html
Bernd
The patch below fixes a typo in the vsx_set_ pattern that causes
wrong code to be generated when using -mcpu=power7. This passed bootstrap
and regression testing on trunk using powerpc64-linux. Ok for trunk?
This is also broken on the 4.7, 4.6 and 4.5 branches, is this ok for
those release branc
Ping!
Any comments on the patch?
Thanks,
Andreas
On 22.12.11 21:44, Andreas Tobler wrote:
Hi all,
the attached patch adds support for powerpc64-*-freebsd*.
Results are/were sent to the test results list.
A few words about the patch.
I have chosen the way to add separate freebsd* files becaus
On Fri, Mar 2, 2012 at 10:57 AM, Peter Bergner wrote:
> The patch below fixes a typo in the vsx_set_ pattern that causes
> wrong code to be generated when using -mcpu=power7. This passed bootstrap
> and regression testing on trunk using powerpc64-linux. Ok for trunk?
>
> This is also broken on t
On Fri, Mar 2, 2012 at 11:04 AM, Andreas Tobler wrote:
>> the attached patch adds support for powerpc64-*-freebsd*.
>> Results are/were sent to the test results list.
>>
>> A few words about the patch.
>> I have chosen the way to add separate freebsd* files because FreeBSD
>> supports not as much
Hello!
i386 maintains stable ABI by passing "unsupported" SSE modes in hard
SSE registers, even if original mode does not fit there. This works
quite well for 32bit targets (-msse2 vs -msse), but 64bit targets
assume SSE2 by default, so various paths aren't well tested for
-mno-sse2.
Attached pat
On Fri, Mar 02, 2012 at 05:32:18PM +0100, Uros Bizjak wrote:
> Patch was tested on x86_64-pc-linux-gnu {,-m32}. Patch was committed
> to mainline, is it OK to commit to 4.7 after it opens?
Have you done any compat testing against compiler without that change
(using ALT_CC_UNDER_TEST=/whatever/gcc
I have committed a patch to libgo to update to the weekly.2012-02-14
release. As usual, in this e-mail message I only include the patches to
files specific to the gccgo version of libgo. Bootstrapped and ran Go
testsuite on x86_64-unknown-linux-gnu. Committed to mainline.
Ian
diff -r 86886691a
On Fri, Mar 2, 2012 at 5:36 PM, Jakub Jelinek wrote:
> On Fri, Mar 02, 2012 at 05:32:18PM +0100, Uros Bizjak wrote:
>> Patch was tested on x86_64-pc-linux-gnu {,-m32}. Patch was committed
>> to mainline, is it OK to commit to 4.7 after it opens?
>
> Have you done any compat testing against compil
... removes extra "extern."
-benjamin2012-03-02 Benjamin Kosnik
* include/c_global/cstdio: Remove extraneous extern.
* include/c_std/cstdio: Same.
diff --git a/libstdc++-v3/include/c_global/cstdio b/libstdc++-v3/include/c_global/cstdio
index d11743a..e648475 100644
--- a/libstdc++-
On Fri, Mar 2, 2012 at 5:40 PM, Uros Bizjak wrote:
>>> Patch was tested on x86_64-pc-linux-gnu {,-m32}. Patch was committed
>>> to mainline, is it OK to commit to 4.7 after it opens?
>>
>> Have you done any compat testing against compiler without that change
>> (using ALT_CC_UNDER_TEST=/whatever
Just fixed a missing subsection in libitm's texinfo docs.
OK for trunk? If so, I'd also think it would be good if this could
still get added to 4.7 (sorry for missing the deadline).
commit e50b0c9e610fdefce5063de0b88cee6c842694e5
Author: Torvald Riegel
Date: Fri Mar 2 18:07:16 2012 +0100
On Fri, Mar 02, 2012 at 11:19:15AM -0500, David Edelsohn wrote:
> On Fri, Mar 2, 2012 at 10:57 AM, Peter Bergner wrote:
> > The patch below fixes a typo in the vsx_set_ pattern that causes
> > wrong code to be generated when using -mcpu=power7. This passed bootstrap
> > and regression testing on
On 03/02/2012 09:10 AM, Torvald Riegel wrote:
> libitm: Update texinfo docs.
>
> libitm/
> * libitm.texi: Link to specification and add a usage example.
I would think this should still be ok for 4.7...
r~
Benjamin De Kosnik writes:
>> I was surprised to see GLIBCXX_3.4.15 symbols added, but then realized
>> you added the complete set so this seems fine.
>
> I meant to say: surprised to see GLIBCXX_3.4.16 symbols added, but then
> you the complete set so this seems fine. So the only added symbols
On Mar 2, 2012, at 1:33 AM, Richard Guenther wrote:
>> Interestingly, the C++ frontend also has a pointer_diff function, but
>> doesn't seem to attempt to optimize. Is there a reason for this?
>
> Frontends should not optimize when they are not required to.
Actually, the frontends should optimize
Hi,
This patch adds --with-abi= support to x86_64-*-* to configure GCC with
--with-abi=x32
--with-abi=mx32
--with-multilib-list=mx32
to set the default ABI to x32. In i386 backend, ISA_64BIT is used to
generate i386 code or x86-64 code. This patch adds a new bit,
ISA_X86_64 to generate 32bit x
On Fri, Mar 02, 2012 at 09:35:18AM -0800, Richard Henderson wrote:
> On 03/02/2012 09:10 AM, Torvald Riegel wrote:
> > libitm: Update texinfo docs.
> >
> > libitm/
> > * libitm.texi: Link to specification and add a usage example.
>
> I would think this should still
On 02/28/2012 07:16 AM, Oleg Endo wrote:
> Wouldn't it make sense to use the value behind
> TARGET_ATOMIC_TEST_AND_SET_TRUEVAL in optabs.c
> (expand_atomic_test_and_set) instead of const1_rtx when emitting
> generated atomic_exchange / atomic_compare_and_swap_exchange_loop?
> Maybe something like t
I've checked in the backports for PR target/49461 and PR boehm-gc/52179 into
the 4.6.x release branch. Thanks Jack.
Index: boehm-gc/configure.ac
===
--- boehm-gc/configure.ac (revision 184807)
+++ boehm-gc/configure.ac (
On Fri, 2012-03-02 at 11:19 -0500, David Edelsohn wrote:
> On Fri, Mar 2, 2012 at 10:57 AM, Peter Bergner wrote:
> > The patch below fixes a typo in the vsx_set_ pattern that causes
> > wrong code to be generated when using -mcpu=power7. This passed bootstrap
> > and regression testing on trunk u
This patch merges template specializations.
* Factored searching out of pph_in_merge_key_tree via a function
parameter. Its name is now pph_in_merge_key_tree_with_searcher. The
decl searching now resides in pph_in_search_key_decl_on_chain and
the type searching now resides in pph_in_search_key_t
Hi,
This patch adds Linux/x32 support to Ada. It sets LIBGNAT_TARGET_PAIRS
similar to Linux/x86-64 and replaces system-linux-x86_64.ads with
system-linux-x86.ads. It also adds "orl $0x0,(%esp)" check for SIGSEGV
probe and sets __gnat_default_libgcc_subdir to libx32 for x32. Tested
on Linux/x32
On Wed, 2012-02-01 at 23:09 -0500, David Edelsohn wrote:
> On Wed, Feb 1, 2012 at 10:00 PM, Peter Bergner wrote:
> > The POWER Toolchain IPC team who is adding POWER7 support to valgrind
> > reminded me that Power ISA 2.06 added a new convert from integer to
> > decimal64 dfp instruction. The fol
Rainer Orth writes:
> Ian Lance Taylor writes:
>
>> This patch to libgo fills out the syscall package for GNU/Linux to match
>> all the functions in the syscall package in the master Go library.
>> There is a test case for this patch at
>> http://code.google.com/p/go/issues/detail?id=3071 . Boo
Ian Lance Taylor writes:
> I have committed a patch to libgo to update to the weekly.2012-02-14
> release. As usual, in this e-mail message I only include the patches to
> files specific to the gccgo version of libgo. Bootstrapped and ran Go
> testsuite on x86_64-unknown-linux-gnu. Committed t
I have committed a patch to update libgo to the weekly.2012-02-22
release. As usual this e-mail message only includes the changes to
gccgo-specific files. Bootstrapped and ran Go testsuite on
x86_64-unknown-linux-gnu. Committed to mainline.
Ian
diff -r a2b8eab75cae libgo/MERGE
--- a/libgo/MERG
Hi,
X32 may generate
movl$-18874240, %eax
movl(%eax), %eax
This patchs allows $-18874240. OK for trunk?
Thanks.
H.J.
---
2012-02-10 H.J. Lu
PR target/52146
* gcc.target/i386/pr52146.c: Update final-scan to allow $-18874240.
diff --git a/gcc/testsui
On Fri, 2012-03-02 at 10:11 -0800, Richard Henderson wrote:
> For proper binary compatibility, we should probably introduce that asap.
> You forgot two things in your patch, gen_int_mode and the fact that we
> still have to return a boolean (0/1) value.
Ah, yes, of course!
>
> Also in order for
On Sat, Nov 12, 2011 at 9:32 AM, Uros Bizjak wrote:
> On Sat, Nov 12, 2011 at 3:19 AM, H.J. Lu wrote:
>
>> The current x32 implementation uses LEAs to convert 32bit address to
>> 64bit. However, we can use addr32 prefix to use 32bit address directly.
>> It improves performance by 5% in SPEC CPU
Hi Jason,
you may remember a patch I posted and over which we exchanged a few messages:
first message: http://gcc.gnu.org/ml/gcc-patches/2010-07/msg02143.html
last message: http://gcc.gnu.org/ml/gcc-patches/2010-09/msg01289.html
I eventually dropped the ball and nothing was installed, although
On 03/02/2012 12:27 PM, Oleg Endo wrote:
> + This value is used by optabs.c atomic op expansion code as well as in
> + sync.md. It must be defined as signed char here or else the movqi
> + pattern will refuse to load it as a QImode constant. */
> +#undef TARGET_ATOMIC_TEST_AND_SET_TRUEVAL
X86-64 linker optimizes TLS_MODEL_INITIAL_EXEC to TLS_MODEL_LOCAL_EXEC
by checking
movq foo@gottpoff(%rip), %reg
and
addq foo@gottpoff(%rip), %reg
It uses the REX prefix to avoid the last byte of the previous
instruction. With 32bit Pmode, we may not have the REX prefix and
the
Hi,
We only need to handle zero-extended addresses in DImode.
OK for trunk?
BTW, all my 10 addr32 patches are tested on Linux/x86-64.
Thanks.
H.J.
---
2012-03-02 H.J. Lu
* config/i386/i386.c (ix86_print_operand_address): Only handle
zero-extended DImode addresses.
diff --g
On Fri, 2012-03-02 at 12:34 -0800, Richard Henderson wrote:
> On 03/02/2012 12:27 PM, Oleg Endo wrote:
> > + This value is used by optabs.c atomic op expansion code as well as in
> > + sync.md. It must be defined as signed char here or else the movqi
> > + pattern will refuse to load it as
This fixes an edge case in parsing summary lines. Some times, the
description field is missing (e.g., 'FAIL: libstdc++/abi_check'), so
the space that the pattern was looking for does not exist.
I've changed it to match any whitespace, which includes '\n'. I also
made it print the line that it fa
On Fri, Nov 11, 2011 at 11:04 AM, H.J. Lu wrote:
> Hi,
>
> I am working on 32bit Pmode for x32:
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50797
>
> It removes all LEAs, which convert 32bit address to 64bit, and uses 0x67
> address prefix instead. I got 5% speed up in SPEC CPU 2K/2006.
>
> B
Rainer Orth writes:
> The first mmap arg is caddr_t (char *), while byte * is uint8 *.
> Casting to void * fixes this.
Thanks.
Committed.
Ian
Hi,
Since the 0x67 address prefix only zeros out the upper 32bits of the
(reg) part in address fs:(reg), we can't use fs:(reg) as memory operand
for x32 with Pmode == SImode. We have to load the address into a
register first and use it as memory operand. Tested on Linux/x86-64.
OK for trunk?
Th
Since stack register may be in SImode for TARGET_64BIT, this patch
checks Pmode to set adjust_stack_insn. OK for trunk?
Thanks.
H.J.
--
2012-03-02 H.J. Lu
* config/i386/i386.c (ix86_expand_prologue): Check Pmode to set
adjust_stack_insn.
diff --git a/gcc/config/i386/i386.c
Hi,
This patches uses word_mode instead of Pmode in loop expand since
word_mode may have bigger size than Pmode. OK for trunk?
Thanks.
H.J.
---
2012-03-02 H.J. Lu
* config/i386/i386.c (ix86_expand_movmem): Use word_mode instead
of Pmode on loop.
(ix86_expand_setmem):
Hi,
Since stack register may be in SImode for TARGET_64BIT, this patch
checks Pmode to adjust stack in proper mode. OK for trunk?
Thanks.
H.J.
---
2012-03-02 H.J. Lu
* config/i386/i386.c (pro_epilogue_adjust_stack): Check Pmode
instead of TARGET_64BIT.
diff --git a/gcc/con
Rainer Orth writes:
> Rainer Orth writes:
>
>> Ian Lance Taylor writes:
>>
>>> This patch to libgo fills out the syscall package for GNU/Linux to match
>>> all the functions in the syscall package in the master Go library.
>>> There is a test case for this patch at
>>> http://code.google.com/p/
Hi,
This patch switches Pmode to SImode for x32. It uses proper patterns
for x32. OK for trunk?
Thanks.
H.J.
---
2012-03-02 H.J. Lu
* config/i386/i386.c (ix86_option_override_internal): Properly
set ix86_gen_leave and ix86_gen_monitor. Check Pmode == DImode.
(legi
Hi,
This is the last patch for Pmode == SImod in x32. In x32, the return value
of the symbol address must be zero-extended to DImode, This patch adds
*zero_extendsidi2_x32 to load the address of a symbol in SImode and
zero-extend it to DImode. It works for x32 since the address size is 32bit.
OK f
Hi all,
I'll offer my first patch to the new 4.8 trunk. I noticed that the -fbacktrace
option and the GFORTRAN_ERROR_BACKTRACE environment variable are somewhat
inconsistently handled. Currently, the environment variabled doesn't actually
override the compilation option, as it should. So, I set
Richard Henderson wrote:
> For proper binary compatibility, we should probably introduce that asap.
> You forgot two things in your patch, gen_int_mode and the fact that we
> still have to return a boolean (0/1) value.
>
> Also in order for the binary compatibility to work right, you'd want to
>
On 30/09/2011, at 1:11 AM, Bernd Schmidt wrote:
...
>
> The following patch rewrites essentially all the cond_exec support in
> ifcvt; reviewing is probably easier if it's thought of as new code.
Kudos for improving if-conversion!
I reviewed this patch to the extent I know ifcvt.c, which is belo
On Fri, 2 Mar 2012, Richard Earnshaw wrote:
> This patch documents some more of the changes that have occurred on
> ARM this year. I've also re-worded a couple of the existing changes
> recorded there to try and improve the clarity to users.
That's quite a bit of a list of improvements. Nice!
>
Dear Tobias,
This is certainly OK for 4.8.
I have a couple of remarks:
(i) The DTYPE_TYPE_MASK is 0x38 so that we saturated it a long time
since! At the moment it does not cause any problems because of the
extremely limited use of the dtype 'type'. Whilst the array
descriptor revamp will elimin
PR 36044 (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36044) is an enhancement
request for a way to display backtraces from user code. I'm against adding yet
another nonstandard intrinsic for this purpose (which is how Intel Fortran does
it), but I would like to offer the following solution to t
76 matches
Mail list logo
