public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65773] [5 Regression] GCC 5.1 miscompiles LLVM function AArch64InstrInfo::loadRegFromStackSlot()
Date: Wed, 15 Apr 2015 16:58:00 -0000	[thread overview]
Message-ID: <bug-65773-4-kojRBkbn1k@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65773-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
Created attachment 35322
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35322&action=edit
Unreduced save-temps file AArch64InstrInfo.ii.gz

Attaching the (unreduced and compressed) preprocessed source.  So far I haven't
been able to reduce it.  The incorrect code generation can be reproduced with:

$ g++ -O2 -std=c++11 -S AArch64InstrInfo.ii

or with

$ g++ -O1 -std=c++11 -S AArch64InstrInfo.ii

At -O0, there are no calls to
_ZN4llvm12MachineInstr10addOperandERNS_15MachineFunctionERKNS_14MachineOperandE
in the text of the caller, so inlining must be present.  All calls to this
function have reasonable setup code for r3, so -O1 is the minimum optimization
level required to reproduce.

The bad code may be found in the function _ZNK4llvm16AArch64InstrInfo20\
loadRegFromStackSlotERNS_17MachineBasicBlockENS1_15bundle_iteratorINS_12Machine\
InstrENS_14ilist_iteratorIS4_EEEEjiPKNS_19TargetRegisterClassEPKNS_18TargetRegi\
sterInfoE, at the third call to
_ZN4llvm12MachineInstr10addOperandERNS_15MachineFunctionERKNS_14MachineOperandE.


  parent reply	other threads:[~2015-04-15 16:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-15 15:28 [Bug target/65773] New: [5.1 regression] " wschmidt at gcc dot gnu.org
2015-04-15 15:33 ` [Bug target/65773] [5 Regression] " jakub at gcc dot gnu.org
2015-04-15 15:38 ` wschmidt at gcc dot gnu.org
2015-04-15 15:43 ` wschmidt at gcc dot gnu.org
2015-04-15 16:58 ` wschmidt at gcc dot gnu.org [this message]
2015-04-16  1:55 ` hubicka at gcc dot gnu.org
2015-04-16  2:35 ` [Bug tree-optimization/65773] " wschmidt at gcc dot gnu.org
2015-04-16  2:37 ` wschmidt at gcc dot gnu.org
2015-04-16  5:02 ` trippels at gcc dot gnu.org
2015-04-16  7:47 ` rguenth at gcc dot gnu.org
2015-04-16  8:18 ` hubicka at gcc dot gnu.org
2015-04-16 10:13 ` jakub at gcc dot gnu.org
2015-04-16 10:30 ` jakub at gcc dot gnu.org
2015-04-16 10:56 ` pinskia at gcc dot gnu.org
2015-04-16 11:15 ` james.molloy at arm dot com
2015-04-16 11:42 ` james.molloy at arm dot com

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-65773-4-kojRBkbn1k@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).