public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, fifteen, updated. 8d862ed59a04ccac2b95384932f881e60e65d76b
Date: Sun, 08 Sep 2013 20:50:52 +0200	[thread overview]
Message-ID: <20130908185053.6D9B820F93@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 4526 bytes --]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".

The branch, fifteen has been updated
       via  8d862ed59a04ccac2b95384932f881e60e65d76b (commit)
      from  defd8d008f9f28a3b91964b6fb7a4bfd11ace778 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 8d862ed59a04ccac2b95384932f881e60e65d76b
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Sun Sep 8 20:50:29 2013 +0200

    gcc: add forgotten patch.

-----------------------------------------------------------------------

Summary of changes:
 src/patches/gcc-4.4.7-texinfo-5.patch | 89 +++++++++++++++++++++++++++++++++++
 1 file changed, 89 insertions(+)
 create mode 100644 src/patches/gcc-4.4.7-texinfo-5.patch

Difference in files:
diff --git a/src/patches/gcc-4.4.7-texinfo-5.patch b/src/patches/gcc-4.4.7-texinfo-5.patch
new file mode 100644
index 0000000..7b2e945
--- /dev/null
+++ b/src/patches/gcc-4.4.7-texinfo-5.patch
@@ -0,0 +1,89 @@
+diff -Naur gcc-4.4.7.org/gcc/doc/cppopts.texi gcc-4.4.7/gcc/doc/cppopts.texi
+--- gcc-4.4.7.org/gcc/doc/cppopts.texi	2008-06-15 11:42:13.000000000 +0200
++++ gcc-4.4.7/gcc/doc/cppopts.texi	2013-09-08 16:50:14.353507748 +0200
+@@ -758,7 +758,7 @@
+ Enable special code to work around file systems which only permit very
+ short file names, such as MS-DOS(a).
+ 
+-(a)itemx --help
++(a)item --help
+ @itemx --target-help
+ @opindex help
+ @opindex target-help
+diff -Naur gcc-4.4.7.org/gcc/doc/c-tree.texi gcc-4.4.7/gcc/doc/c-tree.texi
+--- gcc-4.4.7.org/gcc/doc/c-tree.texi	2009-02-20 16:20:38.000000000 +0100
++++ gcc-4.4.7/gcc/doc/c-tree.texi	2013-09-08 17:53:21.055167463 +0200
+@@ -2338,13 +2338,13 @@
+ not matter.  The type of the operands and that of the result are
+ always of @code{BOOLEAN_TYPE} or @code{INTEGER_TYPE}.
+ 
+-(a)itemx POINTER_PLUS_EXPR
++(a)item POINTER_PLUS_EXPR
+ This node represents pointer arithmetic.  The first operand is always
+ a pointer/reference type.  The second operand is always an unsigned
+ integer type compatible with sizetype.  This is the only binary
+ arithmetic operand that can operate on pointer types.
+ 
+-(a)itemx PLUS_EXPR
++(a)item PLUS_EXPR
+ @itemx MINUS_EXPR
+ @itemx MULT_EXPR
+ These nodes represent various binary arithmetic operations.
+diff -Naur gcc-4.4.7.org/gcc/doc/invoke.texi gcc-4.4.7/gcc/doc/invoke.texi
+--- gcc-4.4.7.org/gcc/doc/invoke.texi	2011-03-23 23:02:12.000000000 +0100
++++ gcc-4.4.7/gcc/doc/invoke.texi	2013-09-08 17:10:49.503066254 +0200
+@@ -4645,11 +4645,11 @@
+ @option{-fdump-rtl-ce3} enable dumping after the three
+ if conversion passes. 
+ 
+-(a)itemx -fdump-rtl-cprop_hardreg
++(a)item -fdump-rtl-cprop_hardreg
+ @opindex fdump-rtl-cprop_hardreg
+ Dump after hard register copy propagation.
+ 
+-(a)itemx -fdump-rtl-csa
++(a)item -fdump-rtl-csa
+ @opindex fdump-rtl-csa
+ Dump after combining stack adjustments.
+ 
+@@ -4660,11 +4660,11 @@
+ @option{-fdump-rtl-cse1} and @option{-fdump-rtl-cse2} enable dumping after
+ the two common sub-expression elimination passes.
+ 
+-(a)itemx -fdump-rtl-dce
++(a)item -fdump-rtl-dce
+ @opindex fdump-rtl-dce
+ Dump after the standalone dead code elimination passes.
+ 
+-(a)itemx -fdump-rtl-dbr
++(a)item -fdump-rtl-dbr
+ @opindex fdump-rtl-dbr
+ Dump after delayed branch scheduling.
+ 
+@@ -4709,7 +4709,7 @@
+ @opindex fdump-rtl-initvals
+ Dump after the computation of the initial value sets.
+ 
+-(a)itemx -fdump-rtl-into_cfglayout
++(a)item -fdump-rtl-into_cfglayout
+ @opindex fdump-rtl-into_cfglayout
+ Dump after converting to cfglayout mode.
+ 
+@@ -4739,7 +4739,7 @@
+ @opindex fdump-rtl-rnreg
+ Dump after register renumbering.
+ 
+-(a)itemx -fdump-rtl-outof_cfglayout
++(a)item -fdump-rtl-outof_cfglayout
+ @opindex fdump-rtl-outof_cfglayout
+ Dump after converting from cfglayout mode.
+ 
+@@ -4751,7 +4751,7 @@
+ @opindex fdump-rtl-postreload
+ Dump after post-reload optimizations.
+ 
+-(a)itemx -fdump-rtl-pro_and_epilogue
++(a)item -fdump-rtl-pro_and_epilogue
+ @opindex fdump-rtl-pro_and_epilogue
+ Dump after generating the function pro and epilogues.
+ 


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2013-09-08 18:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20130908185053.6D9B820F93@argus.ipfire.org \
    --to=git@ipfire.org \
    --cc=ipfire-scm@lists.ipfire.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