public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug optimization/14312] [tree-ssa] [regression] tailcalls not being generated when functions contain pointers Date: Fri, 27 Feb 2004 12:38:00 -0000 [thread overview] Message-ID: <20040227123801.29408.qmail@sources.redhat.com> (raw) In-Reply-To: <20040227010444.14312.rearnsha@gcc.gnu.org> ------- Additional Comments From rth at gcc dot gnu dot org 2004-02-27 12:37 ------- Diego, the problem here is that we reject FOO for tail-call optimization because we find "TMT.1" is a "local variable" with TREE_ADDRESSABLE set. Clearly we need to be ignoring memory tags. Will you please invent a way to recoginize them and ignore them in suitable_for_tail_opt_p? -- What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |dnovillo at gcc dot gnu dot |dot org |org Status|NEW |ASSIGNED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14312
next prev parent reply other threads:[~2004-02-27 12:38 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-02-27 1:04 [Bug optimization/14312] New: [tree-ssa regression] " rearnsha at gcc dot gnu dot org 2004-02-27 1:05 ` [Bug optimization/14312] " rearnsha at gcc dot gnu dot org 2004-02-27 2:01 ` [Bug optimization/14312] [tree-ssa] [regression] " pinskia at gcc dot gnu dot org 2004-02-27 12:38 ` rth at gcc dot gnu dot org [this message] 2004-02-27 13:16 ` dnovillo at redhat dot com 2004-02-27 18:39 ` cvs-commit at gcc dot gnu dot org 2004-02-27 18:45 ` dnovillo at gcc dot gnu dot org 2004-03-04 3:00 ` dnovillo at gcc dot gnu dot org 2004-03-07 2:03 ` pinskia at gcc dot gnu dot org 2004-03-09 15:05 ` dnovillo 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=20040227123801.29408.qmail@sources.redhat.com \ --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).