public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/56258] Please upgrade doc/*.texi to the latest texinfo package(s)
Date: Wed, 20 Feb 2013 12:08:00 -0000 [thread overview]
Message-ID: <bug-56258-4-GgpKs97Ots@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56258-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56258
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-02-20 12:07:36 UTC ---
http://koji.fedoraproject.org/koji/getfile?taskID=5033640&name=build.log
lists lots of warnings and some errors.
--- gcc/ada/gnat-style.texi.jj 2012-08-10 12:57:33.000000000 +0200
+++ gcc/ada/gnat-style.texi 2013-02-20 13:06:03.042667300 +0100
@@ -42,7 +42,7 @@ Texts. A copy of the license is include
@titlepage
@titlefont{GNAT Coding Style:}
@sp 1
-@title @hfill A Guide for GNAT Developers
+@title A Guide for GNAT Developers
@subtitle GNAT, The GNU Ada Compiler
@versionsubtitle
@author Ada Core Technologies, Inc.
--- gcc/doc/invoke.texi.jj 2013-01-31 22:57:22.000000000 +0100
+++ gcc/doc/invoke.texi 2013-02-20 13:06:47.516405739 +0100
@@ -5612,7 +5612,7 @@ Dump after the peephole pass.
@opindex fdump-rtl-postreload
Dump after post-reload optimizations.
-@itemx -fdump-rtl-pro_and_epilogue
+@item -fdump-rtl-pro_and_epilogue
@opindex fdump-rtl-pro_and_epilogue
Dump after generating the function prologues and epilogues.
is an untested guess for fixing the errors.
next prev parent reply other threads:[~2013-02-20 12:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 21:07 [Bug bootstrap/56258] New: " gcc@Denis-Excoffier.org
2013-02-10 12:26 ` [Bug bootstrap/56258] " rguenth at gcc dot gnu.org
2013-02-18 21:32 ` bdubbs at linuxfromscratch dot org
2013-02-20 12:08 ` jakub at gcc dot gnu.org [this message]
2013-02-21 9:42 ` jakub at gcc dot gnu.org
2013-02-21 9:44 ` jakub at gcc dot gnu.org
2013-02-21 9:56 ` jakub at gcc dot gnu.org
2013-02-22 2:01 ` howarth at nitro dot med.uc.edu
2013-02-22 2:03 ` howarth at nitro dot med.uc.edu
2013-02-22 5:00 ` howarth at nitro dot med.uc.edu
2013-02-22 15:19 ` howarth at nitro dot med.uc.edu
2013-03-10 8:07 ` gcc@Denis-Excoffier.org
2013-03-20 11:02 ` rguenth at gcc dot gnu.org
2013-03-20 11:09 ` rguenth at gcc dot gnu.org
2013-03-20 11:16 ` rguenth at gcc dot gnu.org
2013-03-20 11:16 ` rguenth at gcc dot gnu.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=bug-56258-4-GgpKs97Ots@http.gcc.gnu.org/bugzilla/ \
--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).