From: Jeff Law <law@redhat.com>
To: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Martin Jambor <mjambor@suse.cz>, Alexander Monakov <amonakov@ispras.ru>
Subject: Re: [RFC][PATCH] Stabilize a few qsort comparison functions
Date: Tue, 12 Jun 2018 21:49:00 -0000 [thread overview]
Message-ID: <2960ceae-6f79-1252-7105-8e3f83d9f8bc@redhat.com> (raw)
In-Reply-To: <59816ffe-61ea-c887-14f7-1ff11c8574ef@lauterbach.com>
On 02/07/2018 09:58 AM, Franz Sirl wrote:
> Hi,
>
> this is the result of an attempt to minimize the differences between the
> compile results of a Linux-based and a Cygwin64-based powerpc-eabi cross
> toolchain.
> The method used was:
>
> Â Â Â - find the -fverbose-asm assembler files that differ
> Â Â Â - compile that file again on both platforms with
> Â Â Â Â Â Â -O2 -g3 -fdump-tree-all-all -fdump-rtl-all -fdump-noaddr
> Â Â Â - look for the first dump file with differences and check that pass
> Â Â Â Â Â for qsort's
> Â Â Â - stabilize the compare functions
>
> With some help on IRC to better understand the passes and some serious
> debugging of GCC I came up with this patch. On the tested codebase the
> differences in the assembler sources are now down to 0.
> If the various pass maintainers have better ideas on how to stabilize
> the compare functions, I'll be happy to verify them on the codebase.
> For the SRA patch I already have an alternate version with an additional
> ID member.
>
> Comments?
>
> Bootstrapped on linux-x86_64, no testsuite regressions.
>
> Franz Sirl
>
>
> 2018-02-07Â Franz Sirl <franz.sirl-kernel@lauterbach.com>
>
> Â Â Â * ira-build.c (object_range_compare_func): Stabilize sort.
> Â Â Â * tree-sra.c (compare_access_positions): Likewise.
> Â Â Â * varasm.c (output_object_block_compare): Likewise.
> Â Â Â * tree-ssa-loop-ivopts.c (group_compare_offset): Likewise.
> Â Â Â (struct iv_common_cand): New member.
> Â Â Â (record_common_cand): Initialize new member.
> Â Â Â (common_cand_cmp): Use new member to stabilize sort.
> Â Â Â * tree-vrp.c (struct assert_locus): New member.
> Â Â Â (register_new_assert_for): Initialize new member.
> Â Â Â (compare_assert_loc): Use new member to stabilize sort.
This looks pretty reasonable. I don't think you've contributed much
recently, do you still have write access to the repository?
jeff
next prev parent reply other threads:[~2018-06-12 21:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 16:58 Franz Sirl
2018-02-08 15:33 ` Martin Jambor
2018-06-12 21:49 ` Jeff Law [this message]
2018-06-13 11:50 ` Franz Sirl
2018-06-13 12:47 ` Alexander Monakov
2018-06-13 19:26 ` Jeff Law
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=2960ceae-6f79-1252-7105-8e3f83d9f8bc@redhat.com \
--to=law@redhat.com \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=amonakov@ispras.ru \
--cc=gcc-patches@gcc.gnu.org \
--cc=mjambor@suse.cz \
/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).