public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ubizjak 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: Mon, 05 Oct 2015 09:08:00 -0000 [thread overview] Message-ID: <bug-66697-4-H9dfYK60cn@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 --- Comment #5 from Uroš Bizjak <ubizjak at gmail dot com> --- (In reply to Justas L from comment #4) > I haven't tested this yet, but I understand this global solution would > affect the performance of ALL functions, not only those that interface with > outside code, correct? Yes, but you can always move critical functions to a separate file and compile them with special options. > Wine already assigns the force_align_arg_pointer attribute to vulnerable > functions, so making it work for x86_64 would be the better, less disruptive > solution. TBH, I really don't see the reason against force_align_arg_pointer support on x86_64. I have a patch in testing that enables this attribute also for x86_64 targets. >From gcc-bugs-return-498760-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Oct 05 09:09:53 2015 Return-Path: <gcc-bugs-return-498760-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 29327 invoked by alias); 5 Oct 2015 09:09:52 -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 28967 invoked by uid 48); 5 Oct 2015 09:09:48 -0000 From: "ubizjak 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: Mon, 05 Oct 2015 09:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: ubizjak at gmail dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: ubizjak at gmail dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created Message-ID: <bug-66697-4-2BgjYAiOk7@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-66697-4@http.gcc.gnu.org/bugzilla/> References: <bug-66697-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-SW-Source: 2015-10/txt/msg00315.txt.bz2 Content-length: 294 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66697 --- Comment #6 from Uroš Bizjak <ubizjak at gmail dot com> --- Created attachment 36445 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36445&action=edit Patch that enables force_align_arg_pointer attribute for x86_64 targets >From gcc-bugs-return-498761-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Oct 05 09:42:10 2015 Return-Path: <gcc-bugs-return-498761-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 41734 invoked by alias); 5 Oct 2015 09:42:09 -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 41638 invoked by uid 48); 5 Oct 2015 09:42:05 -0000 From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/67841] error: unable to find a register to spill if all registers are callee-saved Date: Mon, 05 Oct 2015 09:42:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: other X-Bugzilla-Version: 6.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ubizjak at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-67841-4-XvcztdGgbI@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-67841-4@http.gcc.gnu.org/bugzilla/> References: <bug-67841-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-SW-Source: 2015-10/txt/msg00316.txt.bz2 Content-length: 618 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67841 --- Comment #7 from Uroš Bizjak <ubizjak at gmail dot com> --- (In reply to H.J. Lu from comment #6) > ix86_expand_prologue in i386.c has > > /* The computation of the size of the re-aligned stack frame means > that we must allocate the size of the register save area before > performing the actual alignment. Otherwise we cannot guarantee > that there's enough storage above the realignment point. */ > > That is where unaligned SSE load/store in prologue come from. We can also use this code for interrupt handler. >From gcc-bugs-return-498762-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Oct 05 09:57:44 2015 Return-Path: <gcc-bugs-return-498762-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 69327 invoked by alias); 5 Oct 2015 09:57:44 -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 69230 invoked by uid 48); 5 Oct 2015 09:57:40 -0000 From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/67821] [5/6 Regression] ICE in duplicate_ssa_name_range_info Date: Mon, 05 Oct 2015 09:57:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 5.3.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.3 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: priority cf_known_to_work Message-ID: <bug-67821-4-ydRZBcX8ex@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-67821-4@http.gcc.gnu.org/bugzilla/> References: <bug-67821-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/msg00317.txt.bz2 Content-length: 346 https://gcc.gnu.org/bugzilla/show_bug.cgi?idg821 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 |P1 Known to work| |5.2.0
next prev parent reply other threads:[~2015-10-05 9:08 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 [this message] 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 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-H9dfYK60cn@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).