public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: "Martin Liška" <mliska@suse.cz>, gcc-patches@gcc.gnu.org
Cc: dvlasenk@redhat.com, Segher Boessenkool <segher@kernel.crashing.org>
Subject: Re: [PATCH 3/3] Extend -falign-FOO=N to N[:M[:N2[:M2]]]
Date: Wed, 04 Jul 2018 00:20:00 -0000	[thread overview]
Message-ID: <dc3805e1-b39f-f6c1-c642-3a7b4a0cc6bb@redhat.com> (raw)
In-Reply-To: <82d6c10f-22d3-f2e8-c6b9-55cd6469966b@suse.cz>

On 07/03/2018 01:11 PM, Martin Liška wrote:
> On 07/03/2018 10:53 AM, Martin Liška wrote:
>> Thank you Jeff.
>>
>> I found some issues when doing build of all targets
>> (contrib/config-list.mk).
>> I'll update patch and test that affected cross-compilers still produce
>> same output.
> 
> Hello.
> 
> I'm done with testing, I bootstrapped and regtested the patch on
> x86_64-linux and ppc64-linux-gnu.
> I also build all cross compilers we have in contrib/config-list.mk and I
> verified that
> results for gcc/gcc/testsuite/gcc.dg/params/blocksort-part.c source file
> is equal for all cross compilers
> that I touched in the patch. I tested these options:
> 
> -O2
> -O2 -falign-loops=256
> -O2 -falign-loops=256 -falign-functions=512 -falign-labels=1024
> -falign-jumps=2048
> -O2 -falign-loops=1024 -falign-functions=512 -falign-jumps=2048
> -O2 -falign-loops=256 -falign-jumps=2048
> -O2 -falign-loops=100 -falign-functions=200 -falign-labels=300
> -falign-jumps=400
> -O2 -falign-loops=1111 -falign-functions=1112 -falign-labels=1113
> -falign-jumps=1114
> 
> there are no issues except one that are present on current trunk:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86394
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86390
> 
> Is the patchset still ready for approval?
Yes.

jeff

  reply	other threads:[~2018-07-04  0:20 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-25 11:04 [PATCH 0/3] Extend -falign-FOO=N to N[,M[,N2[,M2]]] version 9 marxin
2018-05-25 11:04 ` [PATCH 1/3] Add vec::reverse marxin
2018-05-28 12:13   ` Richard Biener
2018-06-13  1:54   ` Jeff Law
2018-05-25 11:04 ` [PATCH 3/3] Extend -falign-FOO=N to N[:M[:N2[:M2]]] marxin
2018-06-29 19:05   ` Jeff Law
2018-07-03  8:53     ` Martin Liška
2018-07-03  9:55       ` Segher Boessenkool
2018-07-03 10:16         ` Martin Liška
2018-07-03 10:58           ` Segher Boessenkool
2018-07-03 12:51             ` Martin Liška
2018-07-03 13:23               ` Segher Boessenkool
2018-07-03 19:12       ` Martin Liška
2018-07-04  0:20         ` Jeff Law [this message]
2018-05-25 11:08 ` [PATCH 2/3] Temporary remove "at least 8 byte alignment" code from x86 marxin
2018-06-13  2:02   ` Jeff Law
2018-07-03 19:20     ` Martin Liška
  -- strict thread matches above, loose matches on Subject: below --
2017-04-18 18:30 [PATCH 0/3] Extend -falign-FOO=N to N[,M[,N2[,M2]]] version 8 Denys Vlasenko
2017-04-18 18:46 ` [PATCH 3/3] Extend -falign-FOO=N to N[,M[,N2[,M2]]] Denys Vlasenko
2017-04-18 19:12   ` Sandra Loosemore
2017-04-17 15:57 [PATCH 0/3] Extend -falign-FOO=N to N[,M[,N2[,M2]]] version 7 Denys Vlasenko
2017-04-17 16:20 ` [PATCH 3/3] Extend -falign-FOO=N to N[,M[,N2[,M2]]] Denys Vlasenko
2017-04-17 20:02   ` Sandra Loosemore
2017-04-18 18:30     ` Denys Vlasenko
2016-10-12 20:53 [PATCH 0/3] Extend -falign-FOO=N to N[,M[,N2[,M2]]] version 4 Denys Vlasenko
2016-10-12 20:53 ` [PATCH 3/3] Extend -falign-FOO=N to N[,M[,N2[,M2]]] Denys Vlasenko
2016-09-30 17:55 [PATCH 0/3] Extend -falign-FOO=N to N[,M[,N2[,M2]]] version 4 Denys Vlasenko
2016-09-30 17:58 ` [PATCH 3/3] Extend -falign-FOO=N to N[,M[,N2[,M2]]] Denys Vlasenko
2016-10-06  9:47   ` Bernd Schmidt
2016-10-06 18:43     ` Denys Vlasenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dc3805e1-b39f-f6c1-c642-3a7b4a0cc6bb@redhat.com \
    --to=law@redhat.com \
    --cc=dvlasenk@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mliska@suse.cz \
    --cc=segher@kernel.crashing.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).