public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug web/47848] New: invalid -ftree-loop-if-convert-memory-writes flag is mentioned at two places (instead of -ftree-loop-if-convert-stores)
@ 2011-02-22 14:50 zsojka at seznam dot cz
  2011-02-22 17:55 ` [Bug web/47848] " spop at gcc dot gnu.org
  2011-02-22 18:05 ` spop at gcc dot gnu.org
  0 siblings, 2 replies; 3+ messages in thread
From: zsojka at seznam dot cz @ 2011-02-22 14:50 UTC (permalink / raw)
  To: gcc-bugs

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

           Summary: invalid -ftree-loop-if-convert-memory-writes flag is
                    mentioned at two places (instead of
                    -ftree-loop-if-convert-stores)
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: trivial
          Priority: P3
         Component: web
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: zsojka@seznam.cz
                CC: spop@gcc.gnu.org


It seems -ftree-loop-if-convert-memory-writes was renamed to
-ftree-loop-if-convert-stores short before the commit, but
-ftree-loop-if-convert-memory-writes is still mentioned at:

gcc/doc/invoke.texi (only in the summary)

http://gcc.gnu.org/onlinedocs/gcc/Option-Summary.html (is this auto-generated?)


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

* [Bug web/47848] invalid -ftree-loop-if-convert-memory-writes flag is mentioned at two places (instead of -ftree-loop-if-convert-stores)
  2011-02-22 14:50 [Bug web/47848] New: invalid -ftree-loop-if-convert-memory-writes flag is mentioned at two places (instead of -ftree-loop-if-convert-stores) zsojka at seznam dot cz
@ 2011-02-22 17:55 ` spop at gcc dot gnu.org
  2011-02-22 18:05 ` spop at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: spop at gcc dot gnu.org @ 2011-02-22 17:55 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #1 from Sebastian Pop <spop at gcc dot gnu.org> 2011-02-22 17:36:38 UTC ---
Author: spop
Date: Tue Feb 22 17:36:34 2011
New Revision: 170411

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=170411
Log:
Fix PR47848: Do not mention -ftree-loop-if-convert-memory-writes.

2011-02-22  Sebastian Pop  <sebastian.pop@amd.com>

    PR doc/47848
    * doc/invoke.texi: Do not mention -ftree-loop-if-convert-memory-writes.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/doc/invoke.texi


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

* [Bug web/47848] invalid -ftree-loop-if-convert-memory-writes flag is mentioned at two places (instead of -ftree-loop-if-convert-stores)
  2011-02-22 14:50 [Bug web/47848] New: invalid -ftree-loop-if-convert-memory-writes flag is mentioned at two places (instead of -ftree-loop-if-convert-stores) zsojka at seznam dot cz
  2011-02-22 17:55 ` [Bug web/47848] " spop at gcc dot gnu.org
@ 2011-02-22 18:05 ` spop at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: spop at gcc dot gnu.org @ 2011-02-22 18:05 UTC (permalink / raw)
  To: gcc-bugs

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

Sebastian Pop <spop at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED

--- Comment #2 from Sebastian Pop <spop at gcc dot gnu.org> 2011-02-22 17:38:12 UTC ---
Fixed.


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

end of thread, other threads:[~2011-02-22 17:38 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-02-22 14:50 [Bug web/47848] New: invalid -ftree-loop-if-convert-memory-writes flag is mentioned at two places (instead of -ftree-loop-if-convert-stores) zsojka at seznam dot cz
2011-02-22 17:55 ` [Bug web/47848] " spop at gcc dot gnu.org
2011-02-22 18:05 ` spop 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).