Snapshot gcc-5-20151013 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/5-20151013/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 5 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-5
On 10/13/2015 01:06 PM, Jeff Law wrote:
On 10/13/2015 07:12 AM, Dominik Vogt wrote:
In some cases, the work of the cse1 pass is counterproductive, as
we noticed on s390x. The effect described below is present since
at least 4.8.0. Note that this may not become manifest in a
performance issue p
On 10/13/2015 07:12 AM, Dominik Vogt wrote:
In some cases, the work of the cse1 pass is counterproductive, as
we noticed on s390x. The effect described below is present since
at least 4.8.0. Note that this may not become manifest in a
performance issue problem on all platforms. Also note that
On 10/11/2015 04:18 PM, Mikhail Maltsev wrote:
Hi!
SUSE performs periodic testing of GCC and publishes the results on their site:
http://gcc.opensuse.org/ (many thanks for this great job!).
I hope
https://vmakarov.fedorapeople.org/spec/
could be useful for your purposes too.
I've changed in
In some cases, the work of the cse1 pass is counterproductive, as
we noticed on s390x. The effect described below is present since
at least 4.8.0. Note that this may not become manifest in a
performance issue problem on all platforms. Also note that -O1
does not show this behaviour because the r
Hi,
The feedback in this thread was overall positive with good suggestions
on implementation details. I'm starting to work on the first draft,
and plan to post something in 2-4 weeks.
Thanks.
On 28 May 2015 at 11:39, Maxim Kuvyrkov wrote:
> Hi,
>
> Akashi-san and I have been discussing require
On 13/10/15 08:55, Abhishek Aggarwal wrote:
> The return address of the calling function is still at +4 byte offset
> wrt to new frame pointer (%ebp) of 'main' function. However, now the
> first argument of 'main' function may not be at +8 byte offset wrt to
> the new frame pointer of the 'main' fu
I am particularly interested about the placement of these 3 assembly
instructions in 'main' function and the way it changes the stack
memory layout shown in Table 2.2, page 11 of
http://www.uclibc.org/docs/psABI-i386.pdf. This layout shows that
first argument of the called function is at offset of
