public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at physics dot uc dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug optimization/9079] Inline constant function pointers
Date: Tue, 08 Jul 2003 10:46:00 -0000	[thread overview]
Message-ID: <20030708104657.10085.qmail@sources.redhat.com> (raw)
In-Reply-To: <20021228032605.9079.173513@bugs.debian.org>

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9079



------- Additional Comments From pinskia at physics dot uc dot edu  2003-07-08 10:46 -------
Subject: Re:  Inline constant function pointers

On Tuesday, Jul 8, 2003, at 00:50 US/Eastern, doko at cs dot tu-berlin 
dot de wrote:
> ------- Additional Comments From doko at cs dot tu-berlin dot de  
> 2003-07-08 04:50 -------
> Subject: Re: Bug#173513:  Inline constant function pointers
>
> pinskia at physics dot uc dot edu writes:
>> Mark this a dup of bug 3713 which was for c++ but now for all 
>> languages.
>>
>> *** This bug has been marked as a duplicate of 3713 ***
>
> I fail to see a resolution to this report. The call to funk is not
> inlined.

This bug was the same bug as 3713 which means that they were the same 
bug.
Having two bugs referring to the same bug in the database is usually 
not good
because we cannot keep track of which bugs are important and which bugs 
or not
and we also cannot keep track of which bugs get fixed, that is why bugs 
are
marked as duplicates of each other.

I hope this bug gets fixed for the tree-ssa branch which makes working 
on the tree a
lot easier and the it can fold the constant function pointer and then 
maybe inline it.

Thanks,
Andrew Pinski


  parent reply	other threads:[~2003-07-08 10:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20021228032605.9079.173513@bugs.debian.org>
2003-07-08  0:53 ` pinskia at physics dot uc dot edu
2003-07-08  4:50 ` doko at cs dot tu-berlin dot de
2003-07-08 10:46 ` pinskia at physics dot uc dot edu [this message]
2004-04-21  2:38 ` pinskia at gcc dot gnu dot org
2004-04-21  2:38 ` [Bug optimization/9079] [tree-ssa] " pinskia at gcc dot gnu dot org
2004-04-21  2:40 ` pinskia at gcc dot gnu dot org
2004-05-17 16:52 ` [Bug tree-optimization/9079] " pinskia at gcc dot gnu dot org
2004-05-18  3:54 ` pinskia at gcc dot gnu dot org
2004-05-21  1:50 ` cesarb at nitnet dot com dot br
2004-05-22 18:26 ` pinskia at gcc dot gnu dot org
2004-05-24 11:49 ` pinskia at gcc dot gnu dot org
2004-12-13 22:25 ` sxanth at ceid dot upatras dot gr
2005-01-23 15:14 ` steven at gcc dot gnu dot org
2005-01-23 15:18 ` pinskia at gcc dot gnu dot org
2005-02-12 23:08 ` 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=20030708104657.10085.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: 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).