From: Joseph Myers <joseph@codesourcery.com>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: linux-snps-arc@lists.infradead.org, libc-alpha@sourceware.org
Subject: Re: [PATCH v2] ieee754/dbl-64: Reduce the scope of temporary storage variables
Date: Tue, 2 Jun 2020 18:16:24 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.2006021814210.3673@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20200602023223.13823-1-vgupta@synopsys.com>
On Mon, 1 Jun 2020, Vineet Gupta via Libc-alpha wrote:
> Also as suggested by Joseph [1] used --strip and compared the libs with
> and w/o patch and their sizes are exactly same (with gcc 9).
My suggestion was to compare the *contents* of the libraries, not just
their sizes. Either they should be byte-for-byte identical, or if there
are other differences (register allocation, line numbers in assertions,
etc.) a more detailed investigation will be needed.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2020-06-02 18:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 19:43 [PATCH] ieee754/dbl-64: Reduce the scope of temporary storage variables Vineet Gupta
2019-11-11 22:33 ` Joseph Myers
2019-11-11 22:43 ` Vineet Gupta
2019-11-11 22:52 ` Joseph Myers
2020-06-02 2:32 ` [PATCH v2] " Vineet Gupta via Libc-alpha
2020-06-02 18:16 ` Joseph Myers [this message]
2020-06-02 20:31 ` Vineet Gupta via Libc-alpha
2020-06-04 19:08 ` Vineet Gupta via Libc-alpha
2020-06-15 19:09 ` Vineet Gupta via Libc-alpha
2020-06-15 19:43 ` Adhemerval Zanella via Libc-alpha
2020-06-15 19:53 ` Joseph Myers
2020-06-15 20:12 ` Vineet Gupta via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.2006021814210.3673@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-snps-arc@lists.infradead.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).