public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/10153] [3.3/3.4 regression] selection of %dil or %sil on ia32 by valid C source
Date: Thu, 22 Jul 2021 16:15:36 +0000	[thread overview]
Message-ID: <bug-10153-4-OAxZzOUZ9a@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-10153-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andrew Pinski <pinskia@gcc.gnu.org>:

https://gcc.gnu.org/g:8819419ba1d397c0444d89079ec16657a09914fb

commit r12-2473-g8819419ba1d397c0444d89079ec16657a09914fb
Author: Andrew Pinski <apinski@marvell.com>
Date:   Tue Jul 20 11:25:43 2021 -0700

    Fix PR 10153: tail recusion for vector types.

    The problem here is we try to an initialized value
    from a scalar constant. For vectors we need to do
    a vect_dup instead.  This fixes that issue by using
    build_{one,zero}_cst instead of integer_{one,zero}_node
    when calling create_tailcall_accumulator.

    Changes from v1:
    * v2: Use build_{one,zero}_cst and get the correct type before.

    OK? Bootstrapped and tested on aarch64-linux-gnu with no regressions.

    gcc/ChangeLog:

            PR tree-optimization/10153
            * tree-tailcall.c (create_tailcall_accumulator):
            Don't call fold_convert as the type should be correct already.
            (tree_optimize_tail_calls_1): Use build_{one,zero}_cst instead
            of integer_{one,zero}_node for the call of
create_tailcall_accumulator.

    gcc/testsuite/ChangeLog:

            PR tree-optimization/10153
            * gcc.c-torture/compile/pr10153-1.c: New test.
            * gcc.c-torture/compile/pr10153-2.c: New test.

  parent reply	other threads:[~2021-07-22 16:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-10153-4@http.gcc.gnu.org/bugzilla/>
2011-03-30 19:51 ` pinskia at gcc dot gnu.org
2021-07-22 16:15 ` cvs-commit at gcc dot gnu.org [this message]
2024-03-23  6:51 ` aoliva at gcc dot gnu.org
     [not found] <bug-10153-873@http.gcc.gnu.org/bugzilla/>
2006-10-24 16:14 ` pinskia at gcc dot gnu dot org
2007-10-06  7:50 ` schwab at suse dot de
     [not found] <20030319173600.10153.etienne.lorrain@masroudeau.com>
2003-06-12 18:18 ` rth@gcc.gnu.org
2003-10-31 22:11 ` pinskia at gcc dot gnu dot org
2004-02-13 15:13 ` dacut at neolinear dot com
2004-02-14  4:22 ` dacut at neolinear dot com
2005-02-15 23:15 ` pinskia at gcc dot gnu dot 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-10153-4-OAxZzOUZ9a@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).