On Wed, 26 Dec 2018, Andrew Pinski wrote:
> This was what I committed finally. Update for the new cores that was
> added after my previous patch.
Also worth a note in gcc-9/changes.html I assume?
Gerald
On Sun, 7 Oct 2018, Sandra Loosemore wrote:
> This is definitely an improvement. One more tweak I'd make is
>
> s/any of the options specified/the options provided as arguments to the
> attribute/
Thank you, Sandra. I made that additional change.
On Mon, 8 Oct 2018, Martin Liška wrote:
> Yes,
On Sun, 30 Dec 2018, Tom de Vries wrote:
> thanks for finding this.
>
> I build the patch for x86_64 and ran make check in the libbacktrace
> subdirectory of the build directory, results looks good.
Cool, thanks! I went ahead and committed this fix.
Note, that I *may* be offline the next nine d
I could not find an updated link on www.andestech.com, in fact the
reference I could find there was broken as well.
If anyone has an update link, happy to add that again!
Applied for now.
Gerald
Index: readings.html
===
RCS file: /
are recommended against from a usability perspective (and also do
not help search engines).
Committed.
Gerald
2019-07-28 Gerald Pfeifer
* doc/xml/manual/documentation_hacking.xml: Fix broken reference
to the Doxygen manual. Avoid a "here" link on the way.
Fix
Applied.
Gerald
2019-07-28 Gerald Pfeifer
* doc/include/gpl_v3.texi (Copying): Use https for www.gnu.org.
Index: doc/include/gpl_v3.texi
===
--- doc/include/gpl_v3.texi (revision 273850)
+++ doc/include/gpl_v3.texi
...like the others.
Committed.
Gerald
Index: readings.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/readings.html,v
retrieving revision 1.316
diff -u -r1.316 readings.html
--- readings.html 28 Jul 2019 08:54:12 - 1.316
+
Tcl 8.6.1 was released more than half a decade ago, so not much of
a point still documenting this Tcl 8.6 GA regression.
Committed.
Perhaps I'll backport to the GCC 9 branch as well.
Gerald
2019-08-04 Gerald Pfeifer
* doc/install.texi (Prerequisites): Remove reference to Tc
On the way pull the column out of the link text.
Committed.
Gerald
Index: readings.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/readings.html,v
retrieving revision 1.317
diff -u -r1.317 readings.html
--- readings.html 30 Jul 201
I hope with that we've caught everything (and that things are going
to remain stable for a while now).
Commmitted.
Gerald
2019-08-04 Gerald Pfeifer
* doc/xml/manual/documentation_hacking.xml: doxygen.org is now
doxygen.nl.
Index: doc/xml/manual/documentation_hackin
Thanks for carrying us for a while, Dan.
Committed.
Gerald
Index: mirrors.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/mirrors.html,v
retrieving revision 1.255
diff -u -r1.255 mirrors.html
--- mirrors.html7 Oct 2018 12:40:52 -
On Wed, 4 Feb 2015, David Malcolm wrote:
>> That was my plan, yes. :-) I just did that and manually ran
>> the script, and it seems to work.
> Thank you!
>> Still, do you think you can add a bit of error handling such
>> that an issue like the one we had (cf.
>> https://gcc.gnu.org/ml/gccadmin/2
On Wed, 10 Apr 2019, Stafford Horne wrote:
> Committed.
Thanks!
> It turns out I do have CVS access, which is granted along with SVN access.
Yes, you do, and you are very welcome making changes like this
(plus anything that remotely qualifies as obvious). :-)
If you have a recommendation (or pa
On Tue, 30 Jul 2019, Shiva Chen wrote:
> The update link will be
> http://www.andestech.com/en/products-solutions/product-documentation/
Thank you. Restored via the patch below that I just committed.
Gerald
Index: readings.html
===
On Wed, 15 May 2019, Thomas Schwinge wrote:
> Sure, and thanks for having a look.
>
>> On this I'd omit the second link if that's okay with you? (I'm
>> happy to make the change, wanted to check in with you first.)
>
> If you'd like to, then please do.
Done thusly. Committed.
Gerald
Index: ch
On Tue, 11 Jun 2019, Bruce Korb wrote:
> I should probably update the e-address as well. Yes, I still receive
> gnu.org email, but not daily. As infrequent as monthly. Can I do
> something to auto-forward it to an e-address I process daily?
You can log in to fencepost.gnu.org and edit /com/mailer/
Applied. G77 really is a *while* ago now. ;-)
Gerald
Index: index.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/bugs/index.html,v
retrieving revision 1.129
diff -u -r1.129 index.html
--- index.html 31 Jan 2019 09:32:18 - 1.12
Committed.
Gerald
Index: readings.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/readings.html,v
retrieving revision 1.319
diff -u -r1.319 readings.html
--- readings.html 10 Aug 2019 21:04:08 - 1.319
+++ readings.html
Committed.
2019-08-17 Gerald Pfeifer
* doc/include/gpl_v3.texi (Copying): Adjust the link to "Why
not LGPL".
Index: doc/include/gpl_v3.texi
===
--- doc/include/gpl_v3.texi (revision 274599)
+++ d
Committed.
Gerald
2019-08-17 Gerald Pfeifer
* doc/ux.texi (User Experience Guidelines): Update reference.
Index: doc/ux.texi
===
--- doc/ux.texi (revision 274599)
+++ doc/ux.texi (working copy)
@@ -9,7 +9,7
On Tue, 30 Jul 2019, Jan Hubicka wrote:
>> Thanks - can you please update changes.html for it in the 9.2 section?
> There seems to be no GCC 9.2 section yet.
I see one now.
On Tue, 30 Jul 2019, Richard Biener wrote:
> Yes. Looks good to me btw.
Same here. (I would have taken Richard's note as
Committed.
Gerald
Index: bugs/index.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/bugs/index.html,v
retrieving revision 1.130
diff -u -r1.130 index.html
--- bugs/index.html 16 Aug 2019 20:59:00 - 1.130
+++ bugs/index.html
On Fri, 29 Jun 2018, Jeff Law wrote:
> ISTM that if you're reverting something recent of your own that's
> causing failures you ought to be able to revert without waiting.
Indeed. And https://gcc.gnu.org/svnwrite.html#all documents this
in the third items.
(Well, that direct link only works afte
On Thu, 10 Jan 2019, Jonathan Wakely wrote:
>> [ https://gcc.gnu.org/projects/tree-ssa/vectorization.html ]
> I'm not disputing that there could be better documentation, but that
> page is not the place to find it. That page should probably get a
> notice added saying that the project is complete a
all
active release branches.
Committed for now.
Gerald
2019-08-18 Gerald Pfeifer
* doc/install.texi (Specific, bfin): blackfin.uclinux.org is
gone, point to sourceforge.net.
Index: doc/install.texi
===
--- doc/in
loc.h (pmm_malloc.h
> should be ok)?
Very good point, Jakub. Thank you!
Somehow I thought I had submitted this updated patch, but apparently
not so. :-( (This has been on my autotester for ages.)
Okay? And if so, okay for GCC 9 after a while?
Gerald
2019-08-18 Gerald Pfeifer
On Tue, 30 Apr 2019, Martin Liška wrote:
>>> This would fix bug 89770 if/when you commit it, btw:
>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89770
> Thanks for useful comments, I've included all of them (except kB change).
> Feel free to see current version at https://gcc.gnu.org/lists.html
I dug into this, and his site still exists, and he's got a new blog,
alas the older items appear to be gone.
Committed.
Gerald
Index: gcc-4.3/porting_to.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.3/porting_to.html,v
retrieving
Time to rotate some news again.
Committed.
Gerald
Index: index.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/index.html,v
retrieving revision 1.1134
diff -u -r1.1134 index.html
--- index.html 12 Aug 2019 08:46:23 - 1.1134
+++
On Sun, 12 Mar 2017, Gerald Pfeifer wrote:
>> References to dependencies on really, really old versions of
>> binutils (talking 10+ years here) which I think we can remove.
>> Let me follow-up with some of you with concrete suggestions
>> around that.
>
> The al
On Mon, 19 Aug 2019, Marek Polacek wrote:
> I'm of the mind that we should advertise some of the new cool
> C++ changes going into GCC 10, esp. those that are user-visible.
I concur. :-)
> Checking this in.
Thank you!
Gerald
On Mon, 26 Aug 2019, Martin Jambor wrote:
> would the following be a good way to state in changes.html that we
> can fold __builtin_roundeven and expand it on an x86?
> +The following built-in functions have been introduced.
> +
> + __builtin_roundeven for the corresponding function from
> +
Now sure how this could survive when GCJ/libjava were removed.
Committed.
Gerald
Index: codingconventions.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/codingconventions.html,v
retrieving revision 1.91
diff -u -r1.91 codingconventions.
I've had this in my tree for months; time to push this out.
Committed.
Gerald
2019-08-31 Gerald Pfeifer
* doc/generic.texi (Unary and Binary Expressions): Mark up
an instance of TYPE_MIN.
Index: doc/generic
Committed.
Gerald
Index: changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-9/changes.html,v
retrieving revision 1.75
diff -u -r1.75 changes.html
--- changes.html14 Aug 2019 11:18:43 - 1.75
+++ changes.html
microsoft.com redirects the existing link and changed the title of
the document; this adjust both.
Committed.
Jonathan(?), if you could regenerate the libstdc++ online docs, that
would be nice.
Gerald
2019-09-01 Gerald Pfeifer
* doc/xml/manual/policy_data_structures_biblio.xml (COM
On Thu, 29 Aug 2019, Jose E. Marchesi wrote:
> ChangeLog:
>
> * MAINTAINERS: Add myself as the maintainer of the eBPF port.
> Remove myself from Write After Approval section.
Approved.
As in: Approved by the steering committed assuming the patchset passes
technical review. :-)
Thank
No change in terms of contents.
Committed.
Gerald
Index: steering.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/steering.html,v
retrieving revision 1.45
diff -u -r1.45 steering.html
--- steering.html 30 Sep 2018 14:38:47 -
On Tue, 16 Oct 2018, Rainer Orth wrote:
> The following patch documents the Solaris 10 obsoletion in the GCC 9
> changes.html. I've based this on the GCC 4.9 text which allowed for
> obsoletion of several targets. Tested by inspection in Firefox.
>
> Ok to install?
Yes. And technically as main
On Wed, 14 Nov 2018, claz...@gmail.com wrote:
> I've just committed the attached patch containing the news for the ARC
> backend.
Nice! (Both in terms of improvements to the ARC target, and this
release notes update.)
GErald
let alone are obsolete elements in current HTML, and
validator.w3.org hence has been loudly complaining about
projects/cxx-dr-status.html
which Marek kindly added and updated in the last couple of days.
The patch below addresses all 487 validation errors on that page. :-)
Committed (in two p
On Wed, 27 Feb 2019, Tom G. Christensen wrote:
> Latest results for 7.x.
>
> -tgc
>
> Testresults for 7.4.0:
> x86_64-w64-mingw32
Thank you, applied (finally).
Gerald
On Wed, 27 Feb 2019, Tom G. Christensen wrote:
> Latest results for 6.x.
Applied, thank you! Note, I had to manually apply the last
three hunks, since patch somehow did not like the format (w/o
me seeing anything obviously wrong):
> Testresults for 6.5.0:
> hppa2.0w-hp-hpux11.11
> hppa64-hp-
On Sat, 19 Jan 2019, Jakub Jelinek wrote:
>> how about the refinement below?
> LGTM. Thanks.
The context has changed a bit since then (due to links being
added), so I had to manually re-apply the patch and committed
the following now.
Gerald
Index: changes.html
=
Applied.
Gerald
Index: changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.7/changes.html,v
retrieving revision 1.154
diff -u -r1.154 changes.html
--- changes.html11 Dec 2018 04:03:15 - 1.154
+++ changes.html
On Fri, 15 Feb 2019, Sam Tebbs wrote:
> I was looking into this and it seems that the CPU and architecture
> removals have already been documented in the Arm-specific section of the
> GCC 9 changes, so explicitly mentioning that the documentation has been
> removed as well is probably unnecessar
Hi Tom,
I'm afraid this triggers on my (FreeBSD-based) testers:
2019-01-29 Tom de Vries
* install-debuginfo-for-buildid.sh.in: New script.
* Makefile.am (check_PROGRAMS): Add b2test and b3test.
(TESTS): Add b2test_buildid and b3test_dwz_buildid.
* Makefile.in
On Mon, 25 Feb 2019, Kyrill Tkachov wrote:
> Here's a wwwdocs patch mentioning the recently-added support for the Arm
> Neoverse N1 and Neoverse E1 processors. Checked the output on Firefox.
>
> Ok to commit (from an aarch64 perspective)?
Looks good to me, just...
> +Support has been added
On Tue, 26 Feb 2019, Tom de Vries wrote:
>>> Specifically I am now seeing
>>>
>>> gmake[4]: *** No rule to make target 'b3test_dwz_buildid',
>>> needed by 'b3test_dwz_buildid.log'.
> The only way of reproducing it was to deinstall dwz.
:
> Fixed in patch below, committed as trivial.
Great, th
On Thu, 14 Mar 2019, Jonathan Wakely wrote:
> The checksum file uses SHA512 not MD5SUM, so the instructions should be
> updated accordingly.
>
> SInce there's only one tarfile these days (not separate ones for
> gcc-base, gcc-g++, gcc-fortran, etc) it doesn't seem necessary to
> filter out the "O
On Mon, 18 Mar 2019, David Malcolm wrote:
> Here's a patch for the website to add my changes for GCC 9 (bearing
> a strong resemblance to my recent blog post)
Wow, that. is. a. lot! :-)
> -Porting to GCC 8 page and the
> +Porting to GCC 9 page and the
Good catch!
> +
> + GCC's diagnost
Let me include the maintainers for alpha and vax; from a web page
perspective this is clearly fine, but I'm not expert enough on the
technical aspects.
(Richard, Matt, if/once you okay, I can apply the patch so you're
off the hook.)
Gerald
On Sun, 31 Mar 2019, co...@sdf.org wrote:
> As far as I
On Fri, 26 Apr 2019, Martin Liška wrote:
> The patch clarifies that gcc-patches mailing list allows up to 400kB
> size of an email.
Thanks, yes.
As one minor detail, note we have KB in one place and with the
patch would have kB. Technically it's probably KiB, but that
may confuse people more tha
On Mon, 29 Apr 2019, Martin Liška wrote:
The patch clarifies that gcc-patches mailing list allows up to 400kB
size of an email.
>> Maybe drop references to gcc-prs while at it as:
>> https://gcc.gnu.org/ml/gcc/2017-05/msg6.html
> Good idea. I'm going to move multiple legacy mailing li
On Mon, 29 Apr 2019, Nathan Sidwell wrote:
> I've committed this as obvious. The TS section didn't note coroutines
> were in progress.
Thanks, Nathan. You also could have committed it wearing your C++
maintainer hat. ;-)
As a small note, our web pages are mirrored on www.gnu.org and that
site
On Thu, 2 May 2019, Joseph Myers wrote:
> This patch adds a mention of -std=c2x and associated options, and the
> single new C2X feature supported (given the early stage of C2X
> development when we left development stage 1), to the GCC 9 release
> notes.
Nice! Thanks for doing this in time for t
ow, which I committed and also activated on gcc.gnu.org,
should address this.
We can then play with the days of the week the (now) four different
snapshots run, but at least after tonight GCC 9 will have a proper
snapshot again, and after tomorrow we'll start seeing ones for GCC 10.
Gerald
20
On Mon, 6 May 2019, Rainer Orth wrote:
> Better late than never: here's the gcc-9/changes.html update listing
> Solaris improvements. I'm all ears for suggestions about wording or
> markup improvements.
I believe it should be "runtime library", cf.
https://gcc.gnu.org/codingconventions.html .
A
Committed.
Gerald
Index: extensions.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/extensions.html,v
retrieving revision 1.62
diff -u -r1.62 extensions.html
--- extensions.html 30 Sep 2018 14:38:46 - 1.62
+++ extensions.html
On Thu, 2 May 2019, Thomas Schwinge wrote:
> +https://www.openacc.org";>OpenACC support in C, C++, and
> +Fortran continues to be maintained and improved.
> +Most of the OpenACC 2.5 specification is implemented.
> +See the
> +https://gcc.gnu.org/wiki/OpenACC#status-9";>implement
On Sat, 12 Jan 2019, Jakub Jelinek wrote:
> Ok for wwwdocs (or do you suggest something different for the P0941R2
> imlementation status)?
I think that was a question to Jason and Jonathan wrt contents?
Markup-wise this looks fine, and adding those links looks like a
good idea.
Gerald
When migrating from CVS to SVN I already reduced direct references
to CVS/SVN, and expecting a migration to GIT in this decade let me
take the opportunity to generalize/simplify things a bit further.
Committed.
(Perhaps we should also start refering to the more general term
"commit" vs "check in"
Hi Paul,
On Mon, 31 Dec 2018, Paul Hua wrote:
> The attached patch mention Loongson 3a1000 3a2000 3a3000 2k1000 support
> in gcc9.
thanks for putting this together. Only a couple of editorial changes:
Index: changes.html
===
+
+
On Thu, 17 Jan 2019, Andrew Stubbs wrote:
> How's this?
Note the typo in the patch for the main page
Hej Jakub, hej Fortran hackers,
On Wed, 21 Nov 2018, Jakub Jelinek wrote:
> Like this? Ok for trunk/wwwdocs?
>
> 2018-11-21 Jakub Jelinek
>
> * invoke.texi (-fdec-include): Document.
how about the refinement below?
Gerald
Index: gcc-9/changes.html
===
On Thu, 10 Jan 2019, Sam Tebbs wrote:
>> I believe this should also be covered in the GCC 9 release notes
>> at https://gcc.gnu.org/gcc-9/changes.html ?
> Sorry for the late reply. My email filters seem to have stumbled a bit
> so I didn't pick this up until now. Would you suggest adding something
On Thu, 17 Jan 2019, Christophe Lyon wrote:
> Ping? I think that kind of patch is OK for stage4?
Yes, documentation patches are (essentially) always okay.
Gerald
On Thu, 15 Nov 2018, David Malcolm wrote:
> Changed in v2:
> * added test coverage
> * improved docs
> * pass orig_diag_kind to the finalizer callback
>
> Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
> Committed to trunk as r266186.
Mind adding something to the release notes at
uch as x86 this creates a mismatch between %lu
(32-bit) and the third parameter (64-bit).
The patch below addresses it; tested on i586-unknown-freebsd11.3.
Okay?
Gerald
2019-01-20 Gerald Pfeifer
* allocfail.c (main): Increase portability of printf statement.
Index: libbacktrace/a
On Mon, 7 Jan 2019, Jakub Jelinek wrote:
> Apparently my recent patch turned on many non-delegitimized UNSPEC notes
> (it is checking only note, goes away in release builds, but anyway).
I've been seeing the following in my testsuite runs which I didn't
get a month or so ago. Are these due to you
On Sat, 26 Jan 2019, Martin Jambor wrote:
> I'd like to propose the following hunk mentioning -Wabsolute-value in
> changes.html of the upcoming gcc 9. Is it OK?
Lovely^WThanks, ok!
Actually, one question:
> + -Wabsolute-value warns when a wrong absolute value
> + function seems to b
Hi Martin,
On Sat, 26 Jan 2019, Martin Jambor wrote:
>> What is a "wrong absolute value function"? That might be good to
>> show by means of an example? (Also in invoke.texi, which I checked
>> before writing this.)
> I'm not sure how to change the wording, perhaps "...when a used absolute
> val
On Wed, 30 Jan 2019, James Greenhalgh wrote:
> Otherwise OK, though I don't remember if that is for me to OK, or
> someone else.
Yes, it is. :-)
(But I'll also have a look tonight if you want to wait for that
Tamar, but that's only an offer. We can always iterate.)
Gerald
On Wed, 23 Jan 2019, Tamar Christina wrote:
> This patch adds the documentation for Stack clash protection and
> Armv8.3-a support to changes.html for GCC 9.
Some additional notes, all minor, for consideration before you commit.
+The probing interval/guard size can be set by using
+--par
On Fri, 1 Feb 2019, Andre Vieira (lists) wrote:
> This patch adds the documentation to the FPU configuration fixes for
> Cortex-R7 and Cortex-R8 to changes.html for GCC9. See
> https://gcc.gnu.org/ml/gcc-patches/2018-11/msg02183.html
Looks good to me. (And I'm happy to see all those improvement
On Wed, 6 Feb 2019, Tamar Christina wrote:
> I've updated the patch with your suggested changes and have grouped
> the Arm and AArch64 targets a bit.
Thanks, Tamar!
> Ok for commit?
Yes, I had meant to imply this in my original review. :-)
Only note is that this seems to hop from to , skipping
On Fri, 5 Aug 2016, Andrew Pinski wrote:
>> I attached a wrong patch, sending the new one.
> This broke cross aarch64-elf-gnu building.
It also broke native i586-unknown-freebsd10.3 (which features
clang as the system compiler).
/scratch/tmp/gerald/gcc-HEAD/gcc/gcov.c:468:25: error: use of undec
On Fri, 8 Jul 2016, Sameera Deshpande wrote:
> I have created new branch unified-autovect based on ToT.
>
> Please find attached the patch adding information about new branch
> "unified-autovect" in the documentation. Is it ok to commit?
Yes, please!
(Once a branch exists, you don't need to ask
Hi Manish,
On Thu, 30 Jun 2016, Manish Goregaokar wrote:
> * doc/install.texi: Mention download_prerequisites
this is okay (and sorry for the delay, I have unexpectedly
"disappeared" for the month of July).
One suggestion:
> +install the libraries. Alternatively, running
> +@code{contrib/d
On Mon, 8 Aug 2016, Senthil Kumar Selvaraj wrote:
> This doc patch informs the user that a specific (or higher) version of
> binutils is a prerequisite for the fix for a rather vexing bug (PR
> 71151) that was fixed for 6.2.
>
> I've added it to the Caveats section; is there a better place
On Wed, 3 Aug 2016, Martin Liška wrote:
> I've installed (r239066) the script which is used by maintainers to
> update PRs in a batch mode.
I think it would be good to add a comment at the top that
describes what the scripts does and how to invoke the script?
Gerald
Hi Tim,
On Tue, 9 Aug 2016, Tim Semeijn wrote:
> We have added a new mirror in Canada.
>
> IP address is being geolocated in the US but it is actually Canadian. If
> it has to be listed as a US mirror please let me know.
thanks for the heads up! Below is the patch that I just applied,
mirroring
Hi Martin,
On Fri, 12 Aug 2016, Martin Liška wrote:
>> I think it would be good to add a comment at the top that
>> describes what the scripts does and how to invoke the script?
> Sure, what about this?
your patch definitely is a nice improvement. Instead of providing
editorial comments, allow m
Hi Martin,
On Mon, 15 Aug 2016, Martin Liška wrote:
> Ready to be installed?
you ignored (or I guess: missed) the updated patch that I
included in my previous message. Can you use that instead
of your original?
As for the examples, I would omit the output of the script,
since otherwise we'll ne
On Fri, 22 Apr 2016, Chris Gregory wrote:
> https://gcc.gnu.org/codingconventions.html#ExternC
>
> In the `Extern "C"` commentary, the coding conventions says:
>
> Definitions within the body of a namespace are not indented.
>
> This should read
>
> Definitions within the body of an `ex
Hi Bill,
On Wed, 3 Feb 2016, Bill Schmidt wrote:
> The following was applied to the website to record additional GCC 6
> changes for PowerPC. The changes passed XHTML verification.
Thanks for documenting all those changes so diligently!
Somehow I missed this originally, but ran into this now,
On Thu, 16 Jun 2016, Tom G. Christensen wrote:
> Latest results for 6.x
Thanks a bunch, Tom! (Somehow I must have missed this, unlike
the other one, and then I was essentially out for a month, sorry.)
Gerald
Working on something else, I noticed that in news.html we have various
references to libstdc++/ (the libstdc++ "micro site") for further
information. Except there really isn't much further information
there, so let's remove those links.
(This also is in preparation of another, forthcoming patch
Our libstdc++/ page dates back to when libstdc++ was merged into GCC in
2000, 0x10 years ago. It has been a mostly empty shell for most of that
time period and hardly seen any updates in the last decade.
So, after https://gcc.gnu.org/ml/gcc-patches/2016-08/msg01467.html I
suggest to streamline
Hi Ayush,
On Mon, 18 Jul 2016, ayush goel wrote:
> I’m attaching a patch just containing the changes made in the /doc.
a couple of comments.
Index: gnulib-import.texi
===
--- gnulib-import.texi (nonexistent)
+++ gnulib-import.tex
On Fri, 19 Aug 2016, Arnaud Charlet wrote:
>>> Text mode translation should not be done for Cygwin, especially since
>>> it does not support unicode setmode calls. This also fixes ada builds
>>> for Cygwin.
>> Ping?
> Can you send the link to your original submission for easy retrieval?
I'm not
2016-08-22 Gerald Pfeifer
* doc/install.texi (Binaries): www.opencsw.org now uses https.
Applied.
I'll backport to GCC 6 as well, once Richi has unfrozen the branch.
Gerald
Index: gcc/doc/install.texi
===
--- gc
Applied.
Gerald
Index: index.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/benchmarks/index.html,v
retrieving revision 1.35
diff -u -r1.35 index.html
--- index.html 27 May 2016 19:35:42 - 1.35
+++ index.html 22 Aug 2016 11:48
It appears www.superh.com no longer has anything to do with processors,
but poker. Better remove this (old) link.
Applied.
Gerald
Index: gcc-3.1/changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.1/changes.html,v
retrieving r
On Mon, 22 Aug 2016, Jonathan Wakely wrote:
>> So, after https://gcc.gnu.org/ml/gcc-patches/2016-08/msg01467.html I
>> suggest to streamline things, remove this page, and apply the patch
>> below.
> Would this remove the link to the libstdc++ FAQ?
I had actually watched out for that. ;-)
https:
On Mon, 22 Aug 2016, Jonathan Wakely wrote:
There's no reason to have a fixed list of release versions in the
libstdc++ docs which needs updating manually. The page at
https://gcc.gnu.org/onlinedocs already links to the Doxygen docs for
each release, so we can just refer to that.
* doc/x
www.codesourcery.com now redirects to mentor.com, which may be a
bit confusing, but also does seem to have quite a bit about non-free
software, and we've been asked not to link to such sites.
Applied.
Gerald
Index: news/inlining.html
On Mon, 22 Aug 2016, Richard Biener wrote:
> The GNU Compiler Collection version 6.2 has been released.
A user pointed out to me (privately) that there is one reference to
GCC 6.1 on our main page still.
Committed.
Gerald
Index: index.html
=
The link redirected to the Alamden site now, but I found a current
address for the journal.
Applied.
Gerald
Index: readings.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/readings.html,v
retrieving revision 1.252
diff -u -r1.252 reading
On Mon, 22 Aug 2016, Jonathan Wakely wrote:
> So I guess I have no real objection to removing the libstdc++ page.
Based on this, I applied the patch I had posted.
If any of you notices anything to improve upon, let me know and I'll
be happy to work on it.
Gerald
1601 - 1700 of 2893 matches
Mail list logo