public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/47791] New: finish function is using absolute value instead of the #defined one
@ 2011-02-18  0:16 bviyer at gmail dot com
  2011-09-25 14:58 ` [Bug c++/47791] " paolo.carlini at oracle dot com
  2012-01-28  7:18 ` [Bug c++/47791] finish function is using literal value instead of a " pinskia at gcc dot gnu.org
  0 siblings, 2 replies; 3+ messages in thread
From: bviyer at gmail dot com @ 2011-02-18  0:16 UTC (permalink / raw)
  To: gcc-bugs

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

           Summary: finish function is using absolute value instead of the
                    #defined one
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: bviyer@gmail.com


GCC Version: GCC 4.6.0-20101211-experimental

In couple places, the parameters passed into "finish_function" is the absolute
value and not the "#define"d one. 

E.g. in the "cp_parser_lambda_body" function, finish function is passed in the
number "2" instead of using "SF_INCLASS_INLINE." I think this could cause some
problems in future versions.

Thanks,

Balaji V. Iyer.


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug c++/47791] finish function is using absolute value instead of the #defined one
  2011-02-18  0:16 [Bug c++/47791] New: finish function is using absolute value instead of the #defined one bviyer at gmail dot com
@ 2011-09-25 14:58 ` paolo.carlini at oracle dot com
  2012-01-28  7:18 ` [Bug c++/47791] finish function is using literal value instead of a " pinskia at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: paolo.carlini at oracle dot com @ 2011-09-25 14:58 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #1 from Paolo Carlini <paolo.carlini at oracle dot com> 2011-09-25 14:52:50 UTC ---
It seems to me that the SF_* that you are mentioning actually are meant for
start_preparsed_function, not for finish_function. The latter should probably
have its own FF_* in cp-tree.h and the comment adjusted. At least, this is what
I see in the tree now.


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug c++/47791] finish function is using literal value instead of a #defined one
  2011-02-18  0:16 [Bug c++/47791] New: finish function is using absolute value instead of the #defined one bviyer at gmail dot com
  2011-09-25 14:58 ` [Bug c++/47791] " paolo.carlini at oracle dot com
@ 2012-01-28  7:18 ` pinskia at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2012-01-28  7:18 UTC (permalink / raw)
  To: gcc-bugs

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2012-01-28
            Summary|finish function is using    |finish function is using
                   |absolute value instead of   |literal value instead of a
                   |the #defined one            |#defined one
     Ever Confirmed|0                           |1

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-01-28 05:56:07 UTC ---
Confirmed,


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2012-01-28  5:56 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-02-18  0:16 [Bug c++/47791] New: finish function is using absolute value instead of the #defined one bviyer at gmail dot com
2011-09-25 14:58 ` [Bug c++/47791] " paolo.carlini at oracle dot com
2012-01-28  7:18 ` [Bug c++/47791] finish function is using literal value instead of a " pinskia at gcc dot gnu.org

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).