From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id A747A3857C40; Wed, 12 Aug 2020 15:42:05 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A747A3857C40
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1597246925;
 bh=sWOmLBwSEnoPPwyq2LMLQrZkr8SR7a4/+jMAVTMIfcc=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=YY583rihS1PWA5eVQw4ZzJa9jwgV99mBnknrY01TZmEQYLriwOO96nXTi3Hl8nFWG
 9qO5XZCqNC+CNTi8uRQhb3XSDRWXI4YE4AXWT4pejMutv4Z63cKsGoJvP3E6zZBc52
 x6pJS1zBqz8XStbXE8oru2T/uTs0M/edY68KlwHc=
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: remi.andruccioli at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.3
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-96573-4-NwukQjTbzJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-96573-4@http.gcc.gnu.org/bugzilla/>
References: <bug-96573-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Aug 2020 15:42:05 -0000

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

--- 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 f=
rom
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=