public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug web/56736] New: Broken link in http://gcc.gnu.org/gcc-4.8/changes.html
@ 2013-03-26 10:18 felix.gerzaguet at gmail dot com
  2013-03-26 10:41 ` [Bug web/56736] " redi at gcc dot gnu.org
  2013-03-26 11:56 ` jakub at gcc dot gnu.org
  0 siblings, 2 replies; 3+ messages in thread
From: felix.gerzaguet at gmail dot com @ 2013-03-26 10:18 UTC (permalink / raw)
  To: gcc-bugs


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

             Bug #: 56736
           Summary: Broken link in http://gcc.gnu.org/gcc-4.8/changes.html
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: web
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: felix.gerzaguet@gmail.com


Hi,

in the IA-32/x86-64 section I quote:
"
Please refer to the user manual for the list of valid CPU names recognized.
"

The link under the "user manual" words point to 
"
http://gcc.gnu.org/onlinedocs/gcc/X86-Built-in-Functions.html#X86-Built-in-Functions
"

which does no exists.

By the way, the page 
"
http://gcc.gnu.org/onlinedocs/gcc/X86-Built-in-Functions.html
"

does not exists either.


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

* [Bug web/56736] Broken link in http://gcc.gnu.org/gcc-4.8/changes.html
  2013-03-26 10:18 [Bug web/56736] New: Broken link in http://gcc.gnu.org/gcc-4.8/changes.html felix.gerzaguet at gmail dot com
@ 2013-03-26 10:41 ` redi at gcc dot gnu.org
  2013-03-26 11:56 ` jakub at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: redi at gcc dot gnu.org @ 2013-03-26 10:41 UTC (permalink / raw)
  To: gcc-bugs


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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2013-03-26
     Ever Confirmed|0                           |1

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> 2013-03-26 10:41:29 UTC ---
The correct URL is
http://gcc.gnu.org/onlinedocs/gcc/X86-Built_002din-Functions.html#X86-Built_002din-Functions


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

* [Bug web/56736] Broken link in http://gcc.gnu.org/gcc-4.8/changes.html
  2013-03-26 10:18 [Bug web/56736] New: Broken link in http://gcc.gnu.org/gcc-4.8/changes.html felix.gerzaguet at gmail dot com
  2013-03-26 10:41 ` [Bug web/56736] " redi at gcc dot gnu.org
@ 2013-03-26 11:56 ` jakub at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: jakub at gcc dot gnu.org @ 2013-03-26 11:56 UTC (permalink / raw)
  To: gcc-bugs


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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-03-26 11:56:04 UTC ---
Though, of course, it is a bad idea to point to trunk onlinedocs which keeps
changing.  The link should point into gcc-4.8.0 onlinedocs instead, which isn't
going to change anymore.


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

end of thread, other threads:[~2013-03-26 11:56 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-03-26 10:18 [Bug web/56736] New: Broken link in http://gcc.gnu.org/gcc-4.8/changes.html felix.gerzaguet at gmail dot com
2013-03-26 10:41 ` [Bug web/56736] " redi at gcc dot gnu.org
2013-03-26 11:56 ` jakub 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).