On 11/29/2016 06:10 PM, David Malcolm wrote:
[snip]
r242985 seems to have broken the build, for me at least (with texinfo
5.1):
../../src/gcc/doc/install.texi:2199: use braces to give a command as an
argument to @=
make[2]: *** [doc/gccinstall.info] Error 1
The attached patch fixes it.
OK to
On 12/07/2016 11:44 AM, Dmitry Vyukov wrote:
Hello,
Revision 241896 added -fsanitize-address-use-after-scope and enabled
it whenever any sanitizer is enabled. This caused problems for kernel
which does not have necessary callbacks for
-fsanitize-address-use-after-scope. I've added the callbacks
On 12/07/2016 12:30 PM, Dmitry Vyukov wrote:
On Wed, Dec 7, 2016 at 8:23 PM, Sandra Loosemore
wrote:
You need to fix doc/invoke.texi as well to reflect this change.
Done.
Attached updated patch.
The documentation change is OK.
-Sandra
On 12/09/2016 05:48 AM, Richard Sandiford wrote:
This series includes most of the changes in group C from:
https://gcc.gnu.org/ml/gcc/2016-11/msg00033.html
The idea is to add wrapper classes around machine_mode_enum
for specific groups of modes, such as scalar integers, scalar floats,
comp
ll wait a day or two before committing the attached patch,
in case anybody wants to argue that this is the wrong way to categorize it.
-Sandra
2016-12-11 Sandra Loosemore
PR other/16519
gcc/
* doc/invoke.texi (Option Summary): Move -pthread to Linker Options.
(Options for Linking): Do
On 12/11/2016 01:28 PM, Rainer Orth wrote:
Hi Sandra,
PR 16519 notes that -pthread has only ever been documented as an RS6000 and
Solaris 2 option. In fact it's supported by most/all(?) POSIX-flavored
targets, including GNU/Linux, BSD variants, Darwin, etc. It's probably best
to document it as
register load pair. Fixed thusly.
-Sandra
2016-12-11 Sandra Loosemore
gcc/
* config/nios2/nios2.c (nios2_emit_move_sequence): Call copy_rtx
to avoid shared structure error.
Index: gcc/config/nios2/nios2.c
===
--- gcc/config
On 12/11/2016 12:30 PM, John David Anglin wrote:
+@item -mcaller-copies
+@opindex mcaller-copies
+The caller copies function arguments passed by hidden reference. This
+option should be used with care as it is not compatible with the default
+32-bit runtime. However, only aggregates larger tha
On 12/12/2016 04:16 AM, James Greenhalgh wrote:
On Thu, Dec 01, 2016 at 11:09:07AM +, James Greenhalgh wrote:
On Wed, Nov 30, 2016 at 05:58:13PM +, Joseph Myers wrote:
On Wed, 30 Nov 2016, James Greenhalgh wrote:
+@code{_Float16} type defined by ISO/IEC TS18661:3-2005
Add a space a
On 12/12/2016 04:16 AM, James Greenhalgh wrote:
On Wed, Nov 30, 2016 at 02:36:28PM +, James Greenhalgh wrote:
Hi,
As subject - update extend.texi to mention availability of _Float16 types
on ARM and AArch64.
OK?
*ping*
Thanks,
James
2016-11-30 James Greenhalgh
* doc/exten
On 12/12/2016 05:40 PM, Kelvin Nilsen wrote:
@@ -15105,6 +15109,24 @@ If all of the enabled test conditions are false, t
The @code{scalar_test_neg} built-in functions return a non-zero value
if their @code{source} argument holds a negative value.
+The @code{__builtin_byte_in_set} function r
On 12/15/2016 03:27 AM, Jakub Jelinek wrote:
On Thu, Dec 15, 2016 at 11:23:14AM +0100, Andreas Schwab wrote:
On Dez 15 2016, Jakub Jelinek wrote:
So, shall we change also the first 3?
Yes, I'd think so.
So here is it in patch form. Is this ok for trunk?
2016-12-15 Jakub Jelinek
his is all routine cleanup I've done no checking on whether the
remaining documentation is correct, whether the set of documented
features corresponds to those currently implemented, etc.
-Sandra
2016-12-19 Sandra Loosemore
gcc/
* doc/cpp.texi: Clean up anachronistic C99 refere
On 12/20/2016 05:14 AM, James Greenhalgh wrote:
On Tue, Dec 20, 2016 at 11:48:26AM +0100, Richard Biener wrote:
On Mon, Dec 19, 2016 at 6:58 PM, James Greenhalgh
wrote:
On Thu, Dec 8, 2016 at 10:44 PM, Uros Bizjak wrote:
Hello!
Attached patch fixes fall-out from excess-precision improvem
On 04/20/2016 07:42 AM, Koval, Julia wrote:
diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index a5a8b23..82de5bf 100644
--- a/gcc/doc/extend.texi
+++ b/gcc/doc/extend.texi
@@ -5263,6 +5263,83 @@ On x86-32 targets, the @code{stdcall} attribute causes
the compiler to
assume that the call
On 05/11/2016 08:56 AM, Jakub Jelinek wrote:
On Wed, May 11, 2016 at 04:47:46PM +0200, Martin Liška wrote:
Thank you Jakub for the note. What about the second version of the patch?
Thanks,
Martin
>From da688c187067dc5c475a4ab5b844c11c4bcd0494 Mon Sep 17 00:00:00 2001
From: marxin
Date: Wed,
On 05/11/2016 11:02 AM, H.J. Lu wrote:
On Tue, May 10, 2016 at 1:02 PM, Sandra Loosemore
wrote:
Again, this sounds like implementor-speak, and there are grammatical errors
(noun/verb disagreement, missing articles). Do users of this attribute need
to know what instructions the compiler is
On 05/16/2016 05:01 AM, Bin Cheng wrote:
Hi,
This is an obvious patch documenting vect_cond_mixed in sourcebuild.texi. OK?
Thanks,
bin
2016-05-13 bin cheng
* doc/sourcebuild.texi (@item vect_cond_mixed): New item.
Assuming the information is technically correct, the patch looks O
On 05/16/2016 04:35 PM, Jim Wilson wrote:
This is my fifth ping. I just need someone to rubber stamp it so I
can check it in.
The documentation change looks fine, but as a documentation maintainer
only I don't think I can approve changes to a release branch.
-Sandra
On 05/16/2016 05:05 PM, Jim Wilson wrote:
Deletes text claiming that major version changes are rare, and fixes
two misspellings of signaling.
Tested with make info and make dvi.
This looks fine to me.
-Sandra
On 05/17/2016 03:27 AM, Ramana Radhakrishnan wrote:
On Tue, May 17, 2016 at 1:22 AM, Sandra Loosemore
wrote:
On 05/16/2016 04:35 PM, Jim Wilson wrote:
This is my fifth ping. I just need someone to rubber stamp it so I
can check it in.
The documentation change looks fine, but as a
re so I'd expect the 32-bit DWARF-2 EH
support to work exactly the same as in a 32-bit-only x86 configuration.
OK to commit?
-Sandra
2016-05-19 Sandra Loosemore
gcc/
* config/i386/cygming.h (DWARF2_UNWIND_INFO): Allow
--disable-sjlj-exceptions for TARGET_BI_ARCH to select DWARF-2
On 05/19/2016 12:40 PM, Kai Tietz wrote:
Hi,
hopefully this time gmail uses mail-encoding elmz ask for ...
Sorry to object here. I would like to point out that defaulting to
dw2 on 32-bit if SEH is used for 64-bit is nothing good in general.
This is reasoned by the problems existing in dw2 in
On 05/13/2016 09:00 AM, H.J. Lu wrote:
I changed it to
---
@item -mgeneral-regs-only
@opindex mgeneral-regs-only
Generate code that uses only the general-purpose registers. This
prevents the compiler from using floating-point, vector, mask and bound
registers.
---
Here is the updated patch.
On 05/20/2016 09:09 AM, Alexander Monakov wrote:
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index d281975..f0331e2 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -19341,6 +19341,18 @@ offloading execution.
Apply partitioned execution optimizations. This is the defau
On 05/20/2016 10:36 AM, Marek Polacek wrote:
diff --git gcc/doc/invoke.texi gcc/doc/invoke.texi
index f3d087f..5909b9d 100644
--- gcc/doc/invoke.texi
+++ gcc/doc/invoke.texi
@@ -297,7 +297,8 @@ Objective-C and Objective-C++ Dialects}.
-Wsuggest-attribute=@r{[}pure@r{|}const@r{|}noreturn@r{|}for
On 05/20/2016 08:58 AM, Robert Suchanek wrote:
Hi,
The patch changes the default behaviour of the direction in which
the local frame grows for MIPS16.
The code size reduces by about 0.5% in average case for -Os, hence,
it is good to turn the option on by default.
Ok to apply?
Regards,
Robert
On 08/24/2015 11:31 AM, Jeff Law wrote:
On 08/22/2015 01:01 AM, FX wrote:
Attached patch cleans up the list of links we provide for GCC binaries:
- pware.hvcc.edu is dead, no mirror or newer alternative found
- h8300-hms.sourceforge.net is inactive since 2003, carries only gcc
3.2 and 3.3
- sun
On 11/07/2016 05:54 AM, Georg-Johann Lay wrote:
@@ -15261,6 +15262,13 @@ GCC supports the following AVR devices a
@include avr-mmcu.texi
+@item -mabsdata
+@opindex mabsdata
+
+Assume that all data in static stocage can be accessed by LDS / STS
s/stocage/storage/
+inctructions. This option
On 11/08/2016 08:13 PM, Martin Sebor wrote:
The -fprintf-return-value optimization has been disabled since
the last time it caused a bootstrap failure on powerpc64le. With
the underlying problems fixed GCC has bootstrapped fine on all of
powerpc64, powerpc64le and x86_64 and tested with no regre
option does, but I
want to be sure I'm explaining it correctly now.
-Sandra
2016-11-09 Sandra Loosemore
PR c/37998
gcc/
* doc/invoke.texi (Code Gen Options) [-fno-common]: Use correct
terminology. Expand to remove ambiguity.
Index: gcc/doc/invoke.texi
==
On 11/11/2016 08:37 AM, James Greenhalgh wrote:
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index f133b3a..75ff8ec 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -378,7 +378,8 @@ Objective-C and Objective-C++ Dialects}.
-flto-partition=@var{alg} -fmerge-all-constants @
On 11/14/2016 02:55 AM, James Greenhalgh wrote:
On Fri, Nov 11, 2016 at 09:42:32PM -0700, Sandra Loosemore wrote:
On 11/11/2016 08:37 AM, James Greenhalgh wrote:
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index f133b3a..75ff8ec 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc
On 11/16/2016 09:49 AM, Martin Sebor wrote:
I'm looking for an approval of the attached patch.
I've adjusted the documentation based on Sandra's input (i.e.,
documented the negative of the option rather than the positive;
thank you for the review, btw.)
On 11/08/2016 08:13 PM, Martin Sebor wrot
On 11/18/2016 09:01 AM, Martin Sebor wrote:
On 11/17/2016 10:34 PM, Sandra Loosemore wrote:
On 11/16/2016 09:49 AM, Martin Sebor wrote:
I'm looking for an approval of the attached patch.
I've adjusted the documentation based on Sandra's input (i.e.,
documented the negativ
On 11/18/2016 11:52 AM, Martin Sebor wrote:
[snip]
I think it would be be ideal if all the options were sorted the same
way in all sections. Is there some command to have texinfo sort them
for us? If not, can we write a script to sort them, either each time
just before generating the docs or m
On 11/20/2016 01:42 PM, Matthias Klose wrote:
+The options @option{--with-target-bdw-gc-include} and
+@option{--with-target-bdw-gc-include} must always specified together for
+each multilib variant and take precedence over
+@option{--with-target-bdw-gc-include}. If none of these options are
+sp
On 11/21/2016 05:57 AM, Matthias Klose wrote:
--with-target-bdw-gc=/opt/bdw-gc,32=/opt/bdw-gc32
sets the include and lib dirs by appending include and lib to the paths. If you
have options --with-target-bdw-gc-include= and --with-target-bdw-gc-lib= as
well, it overrides the settings done in --w
On 11/21/2016 04:23 PM, Matthias Klose wrote:
On 21.11.2016 18:16, Rainer Orth wrote:
Hi Matthias,
ahh, didn't see that :-/ Now fixed, is this clearer now?
The options @option{--with-target-bdw-gc-include} and
@option{--with-target-bdw-gc-lib} must always specified together for
On 12/16/2015 06:29 AM, James Norris wrote:
Hi,
Attached is the patch to add OpenACC documentation for libgomp.
Ok to commit to trunk?
I have some copy-editing nits. I can't say I'm familiar enough with
this functionality to comment intelligently on the content, though
+To activate t
On 12/29/2015 12:33 AM, Yury Gribov wrote:
Hi all,
this patch reverts invalid documentation change -frandom-seed which was
introduced by myself in r216773 a year ago.
I've checked the generated man and the only test for -frandom-seed
(gcc.dg/pr61868.c).
Ok for trunk? I also want to backport
On 12/29/2015 10:38 AM, Yury Gribov wrote:
On 12/29/2015 08:05 PM, Sandra Loosemore wrote:
[snip]
As a user reading this documentation, I wouldn't understand what kind of
string to use as an argument here, or how GCC actually uses it. (Usually
a "random seed" is something
On 01/01/2016 12:31 PM, Vladimír Čunát wrote:
Hello,
I noticed tiny typos in the docs.
(CC me with replies, please, as I'm not reading the list.)
This patch is fine with an appropriate ChangeLog entry. Generally,
fixing typos in documentation or comments falls under the "obvious
patch" rule,
or profiling, bounds checking,
sanitizers, etc as well as stack checking and stack protection. But,
one thing at a time.
-Sandra
2016-01-01 Sandra Loosemore
gcc/
* doc/extend.texi (Common Function Attributes) : Move
to correct alphabetization of table. Copy-edit and correct
markup.
: L
ing it any more, so I think we should just delete it
entirely instead of documenting it. OK to commit?
-Sandra
2016-01-01 Sandra Loosemore
PR 1078
gcc/cp/
* tree.c (cxx_attribute_table): Remove "com_interface" entry.
(handle_com_interface_attribute): Delete.
I've checked in this patch to address one of the long-standing
documentation bugs reported in PR 1078.
-Sandra
2016-01-01 Sandra Loosemore
PR 1078
gcc/
* extend.texi (Common Function Attributes) : New.
* invoke.texi (Code Gen Options) <-fno-stack-limit>: Add pointer
to co
On 01/02/2016 01:37 AM, Vladimír Čunát wrote:
On 01/02/2016 12:13 AM, Sandra Loosemore wrote:
On 01/01/2016 12:31 PM, Vladimír Čunát wrote:
I noticed tiny typos in the docs.
(CC me with replies, please, as I'm not reading the list.)
This patch is fine with an appropriate ChangeLog
On 01/03/2016 01:00 AM, Vladimír Čunát wrote:
On 01/03/2016 01:08 AM, Sandra Loosemore wrote:
If you don't want to bother with that, or don't have commit access to
the repository, I'll check in the patch on your behalf; just let me
know if you want me to do that.
I do *not* hav
While continuing to poke at PR 1078, I found some more attribute
documentation that was inserted into the wrong place. Fixed thusly.
-Sandra
2016-01-03 Sandra Loosemore
gcc/
* doc/extend.texi (Common Function Attributes): Move docs for
MSP430-specific attributes to
(MSP430 Function
On 01/04/2016 03:17 PM, Martin Sebor wrote:
As discussed in c/69104, the -Winvalid-memory-model option is
not documented in the manual. The attached patch rectifies that.
Thanks for tackling this.
Index: doc/invoke.texi
===
---
On 01/04/2016 05:15 PM, Martin Sebor wrote:
s/built-ins/builtins/ (like in the @refs you used previously)
I thought the @refs were an inconsistency and built-in was
the preferred spelling. That's what someone else pointed
out to me sometime ago and what I see documented in the GCC
Coding Conv
16-01-05 Sandra Loosemore
PR 1078
gcc/
* doc/extend.texi (MicroBlaze Function Attributes): Document
interrupt_handler and fast_interrupt attributes.
Index: gcc/doc/extend.texi
===
--- gcc/doc/extend.texi (revision 232077)
+++ gc
-01-05 Sandra Loosemore
PR 1078
gcc/
* doc/extend.texi (V850 Function Attributes): New section.
(V850 Variable Attributes): New section.
Index: gcc/doc/extend.texi
===
--- gcc/doc/extend.texi (revision 232081)
+++ gcc/doc
I've checked in this patch to add some minimal documentation for the
RL78 "saddr" variable attribute.
-Sandra
2016-01-05 Sandra Loosemore
PR 1078
gcc/
* doc/extend.texi (RL78 Variable Attributes): New section.
Index: gcc/
I've been trying to fill in missing documentation for target-specific
attributes. I'm not 100% sure I've got this one correct. OK to commit?
-Sandra
2016-01-06 Sandra Loosemore
PR 1078
gcc/
* doc/extend.texi (Nvidia PDX Function Attributes): New section.
Index: gcc/
On 01/07/2016 06:48 AM, Nathan Sidwell wrote:
On 01/06/16 23:43, Sandra Loosemore wrote:
I've been trying to fill in missing documentation for target-specific
attributes. I'm not 100% sure I've got this one correct. OK to commit?
thanks.
+as a kernel function, which is c
I am about to start a project to incrementally move chunks of
invoke.texi around to better organize this very long chapter of the
manual. For reference, the current top-level structure looks like this:
@chapter GCC Command Options
@section Option Summary
@section Options Controlling the Kind o
On 01/05/2016 08:47 AM, James Norris wrote:
Hi!
I've updated the original patch after some very helpful
comments from Sandra (thank you, thank you).
OK to commit to trunk?
I'm assuming this is now waiting for technical review? I can give it
another read-through for tech-writing issues but I
into the chapter introduction instead. I did a little bit of editing of
the text in the introduction as well, and rewrote the one reference to
the deleted node so it makes sense without it.
-Sandra
2016-01-12 Sandra Loosemore
gcc/
* doc/invoke.texi (Invoking GCC): Copy-edit. Incorporate i
a for -specs=
(which seems to be more closely related to the other subprocess-related
commands -pipe, -pass-exit-codes, and -wrapper than anything to do with
directories). I've checked in this patch to move the docs around to the
more appropriate sections.
-Sandra
2016-01-12 Sandra L
-Sandra
2016-01-12 Sandra Loosemore
gcc/
* doc/invoke.texi (Spec Files): Move section down in file, past
all command-line option descriptions.
Index: gcc/doc/invoke.texi
===
--- gcc/doc/invoke.texi (revision 232306)
+++ gcc/doc/i
On 01/13/2016 06:28 AM, Jonathan Wakely wrote:
This patch corrects the manual w.r.t the default -std mode for C++,
which changed from -std=gnu++98 to -std=gnu++14 in GCC 6. (I was
slightly surprised to find that -ansi didn't change to mean -std=c++14
at the same time, but now I think that makes s
On 01/13/2016 07:27 AM, Jonathan Wakely wrote:
On 03/10/15 14:00 +0100, Jonathan Wakely wrote:
Here's the latest version of the patch, including the typo fix.
Is this patch OK for trunk?
The original thread faded out, it's split across two months in the
archives:
https://gcc.gnu.org/ml/gcc-p
On 01/13/2016 12:25 PM, Jonathan Wakely wrote:
On 13/01/16 09:53 -0700, Sandra Loosemore wrote:
[snip]
Thanks for doing this. I have a one big question not addressed by
your patch, and few nit-picky tech-writerish comments.
The big question is: the existing text in standards.texi says that
ges to the text, just moved it around.
-Sandra
2016-01-13 Sandra Loosemore
gcc/
* doc/invoke.texi (Code Gen Options): Move section up in file,
before target-specific options. Update menu and option summary
to reflect the new section ordering.
Index: gcc/
so rewrote the @menu
description and introductory blurb for the section to be more generic
and better reflect that nowadays target-specific options do a lot more
than just let you choose the hardware model to compile for.
I've committed this patch.
-Sandra
2016-01-13 Sandra Loosemore
gcc
Part 4 of this series was originally intended to move the section "Using
Precompiled Headers" from invoke.texi to extend.texi. But, as I started
to dig around to decide exactly where its should go, I didn't see a good
place to put it there, either -- extend.texi is still very disorganized.
I'
.
I will commit this patch in a day or two if I don't get any suggestions for
improving it meanwhile.
-Sandra
2016-01-14 Sandra Loosemore
gcc/
* doc/invoke.texi (Invoking GCC): Add new section to menu.
(Option Summary): Update to reflect new section and moved options.
(C++ Dialect Op
On 01/15/2016 01:39 AM, Mikhail Maltsev wrote:
On 01/15/2016 05:17 AM, Sandra Loosemore wrote:
This patch consolidates the documentation of GCC options that add runtime
profiling, error checking, or other instrumentation into a single section.
Currently these are scattered all over
n a couple days unless I hear complaints meanwhile.
-Sandra
2016-01-16 Sandra Loosemore
gcc/
* doc/invoke.texi (Invoking GCC): Add new section to menu.
(Option Summary): Update to reflect new section and moved options.
(C++ Dialect Options): Move -fstats to new section.
(Debugging Options):
On 01/18/2016 10:26 AM, Tom de Vries wrote:
Hi,
This patch introduces an option fopt-info-oacc.
When using the option like this with a kernels region in kernels-loop.c
that parloops does not manage to parallelize:
...
$ gcc kernels-loop.c -S -O2 -fopenacc -fopt-info-oacc-all
...
we get a messa
I think the documentation relating to '-z bndplt' in the GCC manual
description of -fcheck-pointer-bounds is incorrect. It looks like, as
of r225862, the GCC driver is supposed to emit an error message if GCC
was configured with a linker that doesn't support this option and you
pass -mmpx with
.texi documentation for Objective-C had a broken link as well
as needing markup fixes, so I made a pass through that file as well.
-Sandra
2016-01-19 Sandra Loosemore
gcc/
* doc/standards.texi: Copy-editing for grammar, markup, and sentence
flow throughout the file. Fix broken link to Obje
On 01/19/2016 03:24 AM, Ilya Enkovich wrote:
2016-01-19 5:25 GMT+03:00 Sandra Loosemore :
I think the documentation relating to '-z bndplt' in the GCC manual
description of -fcheck-pointer-bounds is incorrect. It looks like, as of
r225862, the GCC driver is supposed to emit an error
On 01/19/2016 08:45 AM, Jan Hubicka wrote:
Hi,
this patch mentiones few user visible changes I can think of. I will
add some quality data on firefox once stage3 closes.
It seems that the optimization section of changes.html deserve some work :)
Honza
Index: changes.html
==
biguation information, but I think
that's irrelevant now in documenting what the current version of GCC
supports.
DWARF maintainers, do you want to look this over for technical
correctness? I'll commit this in a couple days if I don't hear any
objections.
-Sandra
2016-01-1
/vect tests
have been added that fail in the same way. Since it's exactly the same
problem and solution as the previous batch, I've committed the attached
patch as an obvious fix.
-Sandra
2014-12-05 Sandra Loosemore
gcc/testsuite/
* gcc.dg/vect/pr63341-1.c: Remove expl
On 12/04/2014 09:06 AM, Eric Botcazou wrote:
2014-11-19 Sandra Loosemore
gcc/
* simplify-rtx.c (simplify_relational_operation_1): Handle
simplification identities for BICS patterns.
gcc/testsuite/
* gcc.target/aarch64/bics_4.c: New.
OK for mainline
On 11/08/2014 08:57 AM, Sandra Loosemore wrote:
2014-11-08 Sandra Loosemore
Chris Jones
Joshua Conner
gcc/
* config/arm/unknown-elf.h (STARTFILE_SPEC): Add conditional
linking of crtfastmath.o.
* config/arm/linux-eabi.h (STARTFILE_SPEC): Likewise
On 11/14/2014 05:46 PM, Sandra Loosemore wrote:
2014-11-14 Sandra Loosemore
Joshua Conner
Chris Jones
gcc/
* doc/invoke.texi (Option Summary): Add -malign-saved-fp-regs.
(ARM options): Document it.
* config/arm/arm.h
On 12/07/2014 01:52 PM, Sandra Loosemore wrote:
On 11/08/2014 08:57 AM, Sandra Loosemore wrote:
2014-11-08 Sandra Loosemore
Chris Jones
Joshua Conner
gcc/
* config/arm/unknown-elf.h (STARTFILE_SPEC): Add conditional
linking of crtfastmath.o
On 11/19/2014 09:34 PM, Jan Hubicka wrote:
[snip]
As for timeline, I have a workshop next week and need to prepare draft for it.
So ideally I would like to work on this only after the workshop (ending
November 28). I would be also happy to help anyone interested to help (I am
just bit slow on po
I've noticed that the GCC user documentation is quite inconsistent about
the name(s) it uses for i386/x86-64/etc targets. invoke.texi has a
section for "i386 and x86-64 Options", but in other places the manual
uses x86, X86, i?86, i[34567]86, x86_64 (underscore instead of a dash), etc.
I'd be
code for what the default really is). I also did
some light copy-editing.
I've checked this in as an obvious cleanup, since it's boring tech
writer stuff and not a substantive change. ;-)
-Sandra
2015-01-02 Sandra Loosemore
gcc/
* doc/invoke.texi ([-fopt-i
I'll leave fixing that up to somebody who has a deeper
understanding of the code.
-Sandra
2015-01-02 Sandra Loosemore
gcc/
* doc/invoke.texi (Option Summary): Fix spelling of
-fdevirtualize-at-ltrans.
([-fdevirtualize]): Fix markup.
([-fdev
ubstantive
changes, I've checked it in under the obvious fix rule.
-Sandra
2015-01-03 Sandra Loosemore
gcc/
* doc/invoke.texi ([-fplan9-extensions]): Add/fix @opindex.
([-fvtv-debug]): Likewise.
([-Wc++-compat]): Likewise.
([-Wc++11-compat]): Likewise
I spotted some typos in the description of -fsemantic-interposition.
This patch fixes them and also cleans up some awkward grammar.
Committed under the obvious fix rule.
-Sandra
2015-01-03 Sandra Loosemore
gcc/
* doc/invoke.texi ([-fsemantic-interposition]): Fix typos and
Committed under the obvious fix rule, since this is more boring
tech-writer stuff.
-Sandra
2015-01-03 Sandra Loosemore
gcc/
* doc/invoke.texi ([-fisolate-erroneous-paths-dereference]):
Copy-edit description.
([-fisolate-erroneous-paths-attribute]): Likewise.
did minor cleanup on the -fprofile-generate and -fprofile-use
options, which also had some of the same markup problems.
I've committed this under the "obvious fix" rule.
-Sandra
2015-01-03 Sandra Loosemore
gcc/
* doc/invoke.texi ([-fprofile-generate], [-fprofi
I wasn't
really scanning for those at this time.
Patch checked in under the "obvious fix" rule.
-Sandra
2015-01-04 Sandra Loosemore
gcc/
* doc/invoke.texi ([-fsized-deallocation]): Copy-edit to fix
verb tense, etc.
([-fvtable-verify], [-f
ule.
-Sandra
2015-01-05 Sandra Loosemore
gcc/
* doc/invoke.texi: Fix incorrect uses of @code, @option, @samp,
etc markup throughout the file.
Index: gcc/doc/invoke.texi
===
--- gcc/doc/invoke.texi (rev
On 01/05/2015 03:57 PM, Joseph Myers wrote:
On Mon, 5 Jan 2015, Sandra Loosemore wrote:
@file is used for file names.
For standard headers, the use of @code{} (inttypes.h and
limits.h, in this patch) is deliberate, reflecting that the C standard
does not require headers to correspond to
On Tue, 6 Jan 2015, James Greenhalgh wrote:
On Tue, Jan 06, 2015 at 02:56:58PM +, Joseph Myers wrote:
On Tue, 6 Jan 2015, James Greenhalgh wrote:
I was aiming to:
* Remove outdated details of the compiler.
* Remove long or obscure words that, while accurate, only served to
obfusc
On 01/05/2015 04:15 PM, Eric Botcazou wrote:
Hi,
the attached patch removes obsolete ports (c4x, m68hc11 and ms1), toggles the
'p' letter and adjust accordingly (only avr, fr30, m68k, mcore, rs6000 and sh
still use define_peephole) and removes trailing spaces.
OK to commit?
Some ports are miss
Quite some time ago (r184879) I reformatted the entry for the i386
-mrecip= option as part of a general cleanup of that section. Here's
the corresponding change for the very similary RS/6000 option, which
I've committed as an "obvious fix".
-Sandra
2015-01-
like expressions). I also found a few places where @command markup
should be used instead.
-Sandra
2015-01-07 Sandra Loosemore
gcc/
* doc/invoke.texi: Fix incorrect uses of @samp markup throughout
the file where @code, @command, etc is more appropriate.
Index: gc
ass to use a metasyntactic variable instead of putting the keywords
inline, but that's more work and more prone to possible unintended changes.
I've checked this in under the "obvious fix" rule.
-Sandra
2015-01-07 Sandra Loosemore
gcc/
* doc/invoke.texi ([-
e to do so in a few days if I don't hear any
objection or request for more time to review it meanwhile.
-Sandra
2015-01-08 Sandra Loosemore
gcc/
* doc/invoke.texi ([-fvtable-verify]): Copy-edit and fix markup.
([-fvtv-debug], [-fvtv-counts]): Likewise. Correct
On 12/17/2014 03:18 PM, Sandra Loosemore wrote:
On 11/14/2014 05:46 PM, Sandra Loosemore wrote:
2014-11-14 Sandra Loosemore
Joshua Conner
Chris Jones
gcc/
* doc/invoke.texi (Option Summary): Add -malign-saved-fp-regs.
(ARM options): Document it.
* config
On 12/17/2014 03:21 PM, Sandra Loosemore wrote:
On 12/07/2014 01:52 PM, Sandra Loosemore wrote:
On 11/08/2014 08:57 AM, Sandra Loosemore wrote:
2014-11-08 Sandra Loosemore
Chris Jones
Joshua Conner
gcc/
* config/arm/unknown-elf.h (STARTFILE_SPEC): Add
901 - 1000 of 1318 matches
Mail list logo