public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/66697] Feature request: -mstackrealign and force_align_arg_pointer for x86_64 Date: Wed, 07 Oct 2015 10:49:00 -0000 [thread overview] Message-ID: <bug-66697-4-N1NK9j0ySG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66697-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66697 H.J. Lu <hjl.tools at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hjl.tools at gmail dot com --- Comment #20 from H.J. Lu <hjl.tools at gmail dot com> --- (In reply to Uroš Bizjak from comment #19) > (In reply to Justas L from comment #18) > > Out of curiosity, what could it be that makes -mincoming-stack-boundary=3 > > successfully deal with rogue code while -mstackrealign fails at that? > > Shouldn't -mstackrealign do the same job without being told what the outside > > stack alignment is, or am I misunderstanding it? > > -mstackrealign conditionally generates realignment prologue, depending on > presence of insns that require 128bit alignment. It looks that heuristics is > not yet fully reliable on x86_64. Bugreports welcome! -mstackrealign works correctly as designed on x86-64. The issue is MIN_STACK_BOUNDARY. When MIN_STACK_BOUNDARY is 128, you don't need to realign the stack if you only need 128-bit stack alignment. >From gcc-bugs-return-498950-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Oct 07 10:59:24 2015 Return-Path: <gcc-bugs-return-498950-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 2531 invoked by alias); 7 Oct 2015 10:59:24 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 2473 invoked by uid 55); 7 Oct 2015 10:59:19 -0000 From: "vehre at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/65889] [6 Regressions] [OOP] ICE with sizeof a polymorphic variable. Date: Wed, 07 Oct 2015 10:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 6.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vehre at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: vehre at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-65889-4-NDBwAxWxCK@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-65889-4@http.gcc.gnu.org/bugzilla/> References: <bug-65889-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-10/txt/msg00505.txt.bz2 Content-length: 793 https://gcc.gnu.org/bugzilla/show_bug.cgi?ide889 --- Comment #4 from vehre at gcc dot gnu.org --- Author: vehre Date: Wed Oct 7 10:58:46 2015 New Revision: 228566 URL: https://gcc.gnu.org/viewcvs?rev"8566&root=gcc&view=rev Log: gcc/fortran/ChangeLog: 2015-10-07 Andre Vehreschild <vehre@gcc.gnu.org> PR fortran/65889 * trans-intrinsic.c (gfc_conv_intrinsic_sizeof): Handle pointer to and on stack class objects as sizeof parameter. gcc/testsuite/ChangeLog: 2015-10-07 Andre Vehreschild <vehre@gcc.gnu.org> PR fortran/65889 * gfortran.dg/sizeof_5.f90: New test. Added: trunk/gcc/testsuite/gfortran.dg/sizeof_5.f90 Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/trans-intrinsic.c trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2015-10-07 10:49 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-29 20:03 [Bug target/66697] New: " bucaneer at gmail dot com 2015-09-29 4:26 ` [Bug target/66697] " austinenglish at gmail dot com 2015-10-04 15:29 ` ubizjak at gmail dot com 2015-10-04 21:23 ` bucaneer at gmail dot com 2015-10-05 9:08 ` ubizjak at gmail dot com 2015-10-05 17:40 ` ubizjak at gmail dot com 2015-10-05 19:55 ` bucaneer at gmail dot com 2015-10-06 6:40 ` ubizjak at gmail dot com 2015-10-06 9:21 ` ubizjak at gmail dot com 2015-10-06 12:33 ` bucaneer at gmail dot com 2015-10-06 13:45 ` ubizjak at gmail dot com 2015-10-06 16:38 ` bucaneer at gmail dot com 2015-10-06 16:42 ` ubizjak at gmail dot com 2015-10-06 16:53 ` ubizjak at gmail dot com 2015-10-06 23:09 ` bucaneer at gmail dot com 2015-10-07 6:51 ` ubizjak at gmail dot com 2015-10-07 10:49 ` hjl.tools at gmail dot com [this message] 2015-10-07 12:13 ` bucaneer at gmail dot com 2015-10-07 12:17 ` hjl.tools at gmail dot com 2015-10-07 12:21 ` ubizjak at gmail dot com 2015-10-07 17:42 ` uros at gcc dot gnu.org 2015-10-12 16:30 ` uros at gcc dot gnu.org 2015-10-12 16:42 ` ubizjak at gmail 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-66697-4-N1NK9j0ySG@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: linkBe 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).