public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "remi.andruccioli at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/96573] [10/11 Regression] Regression in optimization on x86-64 with -O3
Date: Wed, 12 Aug 2020 15:42:05 +0000	[thread overview]
Message-ID: <bug-96573-4-NwukQjTbzJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96573-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96573

--- Comment #2 from Remi Andruccioli <remi.andruccioli at gmail dot com> ---
Hello,

Thanks for your quick reply and investigations.

I agree this is quite an uncommon need. I use it when I have to deal with
endianness and I/O. So I mainly use it when dumping content and variables from
the memory to files on the disk in a constant endianness across all the
different target machines, for later analysis. (same idea than what is done
with the endianness of network)


Regards,

Remi Andruccioli

  parent reply	other threads:[~2020-08-12 15:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-11 17:45 [Bug c/96573] New: [Regression] Regression in optimization on x86-64 with -O3 from GCC 9 to 10 remi.andruccioli at gmail dot com
2020-08-11 18:22 ` [Bug tree-optimization/96573] [10/11 Regression] Regression in optimization on x86-64 with -O3 jakub at gcc dot gnu.org
2020-08-12 15:42 ` remi.andruccioli at gmail dot com [this message]
2020-08-25  8:44 ` rguenth at gcc dot gnu.org
2021-03-31  9:13 ` rguenth at gcc dot gnu.org
2021-04-01  8:52 ` cvs-commit at gcc dot gnu.org
2021-04-01  9:22 ` [Bug tree-optimization/96573] [10 " jakub at gcc dot gnu.org
2021-04-04 19:42 ` pinskia at gcc dot gnu.org
2021-04-06 10:46 ` cvs-commit at gcc dot gnu.org
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2022-06-28 10:41 ` jakub at gcc dot gnu.org
2023-07-07  9:03 ` rguenth at gcc dot gnu.org

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=bug-96573-4-NwukQjTbzJ@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).