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_hacking.xml
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
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 Tcl 8.6
...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
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
mmended 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 another br
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:
I have seen an increasing number of reports of GCC failing to
build with clang on powerpc (on FreeBSD, though that's probably
immaterial).
Turns out that clang has vec_step as a reserved word on powerpc
with AltiVec.
We OTOH use vec_step s as a variable name in gcc/tree-vect-loop.c.
The best
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 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
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
>
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
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
On Mon, 10 Jun 2019, Martin Liška wrote:
> I'm fine with the Gerald. Thank you for it.
I went ahead and committed this, thanks.
Sandra, if you have any comments still happy to update.
Gerald
On Sun, 9 Jun 2019, Maya Rashish wrote:
> doc/invoke.texi: Update fortran file locations.
Thank you. I added a full ChangeLog entry and committed this to
trunk.
If I had more time, I'd push back to the GCC 9 branch as well;
anyone who wants to pick doc changes and push them?
Gerald
On Sun, 15 Jul 2018, Basile Starynkevitch wrote:
>> Basile, should we generally remove this reference to GCC MELT?
> Yes. I am no more working on MELT, but I did begin to work on its successor:
Sorry for the delay - I finally applied the patch below.
If/when you want that successor to be listed
This is related to changes I made to readings.html one-and-a-half
days ago. Essentially fortran.org underwent quite some changes,
breaking links left and right, and frankly looking a little (too)
commercial.
In any case I could not find what looks like a proper replacement
for this link, so I
www.fortran.org made a number of changes to their site which now
defaults to https, does not carry the FORTRAN 77 Standard any more
(that I could find it), and removed some other material.
This updates readings.html accordingly, and also streamlines the
Fortran section there a bit to reduce
So, this is probably the patch in GCC that's seen the longest delays
between different steps. :-o
On Mon, 30 Jan 2017, Jonathan Wakely wrote:
>> Thanks for doing that, Jonathan!
>>
>> Only one curious question: Why "Supported Releases" on our
>> main page versus "This release is no longer
On Thu, 30 May 2019, Jonathan Wakely wrote:
> I decided to make a few small changes, and ended up rewriting several
> sections. Committed to trunk.
Thank you! That also nicely addressed the changed URLs I had noticed.
Gerald
In some interpretations "not...of all" may not be seen as
100% clear, so I propose to use "not...of any".
On the way fix the grammar in the next sentence.
Sandra, and Martin as the original author, does this makes
sense for you?
Gerald
2019-06-09 Gerald Pfeifer
On Sun, 5 Aug 2018, Florian Weimer wrote:
>> some folks in FreeBSD-land have worked to remove all uses of gets()
>> and in fact the gets() function itself.
>>
>> Generally GCC builds just fine in such an environment, except for
>> libssp where libssp/gets-chk.c has the following:
>>
>>char *
hoard.org is a bit strange in that https is broken (certificate
problem), so switch that back to plain http.
Committed.
Gerald
2019-05-31 Gerald Pfeifer
* doc/xml/manual/allocator.xml: Move hoard.org back to http.
Index: doc/xml/manual/allocator.xml
Writing a commit log for the lang/gcc9 port on FreeBSD I noticed a
few edits around the LTO improvements in the GCC 9 release notes
(which, by the way, was a nice summary).
Honza, I went ahead and committed these, but will be happy to
refine/update should I have misunderstood anything or you'd
...so we should update our link, too.
Committed.
Gerald
Index: readings.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/readings.html,v
retrieving revision 1.312
diff -u -r1.312 readings.html
--- readings.html 26 May 2019 19:39:47
Committed.
(I wish we had better tooling to push changes like this to older
branches more easily.)
Gerald
2019-05-26 Gerald Pfeifer
* doc/xml/manual/appendix_contributing.xml: Update pointer to
C++ standard at ansi.org.
Index: doc/xml/manual/appendix_contributing.xml
Committed.
Gerald
Index: readings.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/readings.html,v
retrieving revision 1.311
diff -u -r1.311 readings.html
--- readings.html 26 May 2019 17:50:01 - 1.311
+++ readings.html
Committed.
(This is really just changing http to https plus reformatting of
this paragraph to avoid overly long lines.)
Gerald
Index: readings.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/readings.html,v
retrieving revision 1.310
The links adjustment I would just have committed right away, but
I'd also like to suggest swe simplify the section: the following
paragraph doesn't really add much, but duplicates the external
link.
Thoughts?
Gerald
2019-05-26 Gerald Pfeifer
* doc/xml/manual/support.xml: Adjust link
a, if you could have another pass that would be really good;
I'm sure you'll be able to further improve.
Gerald
2019-05-26 Gerald Pfeifer
* doc/invoke.texi (Link Options): Many editorial changes around
-flinker-output.
Index: doc/in
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
> +
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
+++
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 .
hich 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
2019-05-04
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
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 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
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
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 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
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
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,
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
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.
*
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
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 ,
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
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
+
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
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
>
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
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
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 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
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, 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
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, 17 Jan 2019, Andrew Stubbs wrote:
> How's this?
Note the typo in the patch for the main page
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
===
+
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
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
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
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 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 Fri, 28 Dec 2018, Gerald Pfeifer wrote:
> The patch below should address this (and does in my tests), though
> my tester seems to have unrelated(?) problems right now, so better
> for one of you to give a spin as well, please.
Now successfully regression tested on i586-unknown-fr
at in addition to FreeBSD this probably also fails on
Solaris and Darwin.
The patch below should address this (and does in my tests), though
my tester seems to have unrelated(?) problems right now, so better
for one of you to give a spin as well, please.
Gerald
2018-12-28 Gerald Pfeifer
On Mon, 26 Nov 2018, Kyrill Tkachov wrote:
> Hi Christoph,
:
> Can you please create a patch for the changes.html page
> (https://gcc.gnu.org/gcc-9/changes.html)
> mentioning the new CPU support? There are examples on that page of the kind of
> appropriate wording.
> You can find details of how
Hi Paul and Matthew,
I believe it would be good to get this and other MIPS changes covered
in the GCC 9 release notes at https://gcc.gnu.org/gcc-9/changes.html .
Gerald
PS: https://gcc.gnu.org/about.html has background how to go about this.
On Wed, 28 Nov 2018, Andre Vieira (lists) wrote:
> Here are the documentation bits I forgot, I've also opened PR 88224 in
> bugzilla for this issue.
>
> Is this OK for trunk and gcc-8 backport?
>
> gcc/ChangeLog:
> 2018-11-28 Andre Vieira
>
> PR target/88224
> *
On Fri, 23 Nov 2018, Sam Tebbs wrote:
> The mtune= documentation in doc/invoke.texi contains some obsolete CPU names
> that have been removed from the Arm and AArch64 backends. This patch removes
> them.
I believe this should also be covered in the GCC 9 release notes
at
At first I was going to change http to https for this link, but
given this is GCC 4.7, simply using a textual reference feels safer.
Applied.
Gerald
Index: gcc-4.7/changes.html
===
RCS file:
Committed.
Gerald
2018-12-10 Gerald Pfeifer
* doc/xml/manual/documentation_hacking.xml: Update reference
to epubcheck.
Index: libstdc++-v3/doc/xml/manual/documentation_hacking.xml
===
--- libstdc++-v3/doc/xml
On Fri, 7 Dec 2018, Iain Buclaw wrote:
> After pushing, it was noticed that there was a small misspelling that
> went unnoticed. I've committed the correction as I don't think
> there'll be any objection to the change.
Indeed. Obvious changes and ones within your domain (so release
notes for
On Sun, 2 Dec 2018, Iain Buclaw wrote:
> I assume that the notes on the about.html page are all that are
> needed to commit and push?
Yes, they *should*.
If you run into anything that's missing or have any questions,
just let me know and I'll (a) help directly and (b) see how to
improve the
Hi Iain,
On Mon, 12 Nov 2018, Iain Buclaw wrote:
> As suggested, this adds an announcement of the D front end addition
> to the news items on the GCC home page, and from what I can tell, the
> relevant pages where the language should get a mention.
I noticed this hasn't gone in; apologies for
On Wed, 14 Nov 2018, claz...@gmail.com wrote:
> I've just committed the attached patch containing the news for the ARC
> backend.
Thanks!
> LRA is now on by default for the ARC target. This can be
> controlled by -mlra.
May that make it sound a bit like one still needs to specify -mlra
to
Applied.
Gerald
Index: readings.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/readings.html,v
retrieving revision 1.307
diff -u -r1.307 readings.html
--- readings.html 1 Dec 2018 19:17:56 - 1.307
+++ readings.html
I've been getting
"A possible equivalent for dz9zr002 was not found." (or similar)
for these two pages for a while.
If you have suitable links to cover these, please go ahead and add
them; for the time being I committed the patch below.
Gerald
Index: readings.html
This one seems to have escaped my http->https changes for openmp.org
the last month(s).
Committed.
Gerald
Index: gcc-4.9/changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.9/changes.html,v
retrieving revision 1.96
diff -u
www.itu.int has moved to https.
Committed.
Gerald
Index: news/chill.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/news/chill.html,v
retrieving revision 1.9
diff -u -r1.9 chill.html
--- news/chill.html 30 Sep 2018 14:38:54 -
Committed.
Gerald
Index: codingconventions.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/codingconventions.html,v
retrieving revision 1.89
diff -u -r1.89 codingconventions.html
--- codingconventions.html 28 Nov 2018 23:39:31 -
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
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
On Thu, 4 Oct 2018, Anthony Green wrote:
> I was building a C compiler from a source tree that does not include
> the sources for the fortran front-end. It seems that this is no longer
> supported, and the fortran sources must be available even if you're only
> building C/C++.
>
> I'll stop
Hi Jakub,
On Fri, 12 Oct 2018, Jakub Jelinek wrote:
> If you have regression bugfixes or documentation fixes that should be
> still backported to the branch, please test them and check them in
> before Friday, October 19th
I'd like to push back
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, 2 Oct 2018, David McCallum wrote:
> At this time, your Canadian mirror site at http://gcc.parentingamerica.com/
> is broken. There is only a page with the text "It works!"... which appears
> to be untrue.
Thanks for letting us know, David!
James, heads up!
For now I committed the patch
On Tue, 2 Oct 2018, David McCallum wrote:
> At this time, your Canadian mirror site at http://gcc.parentingamerica.com/
> is broken. There is only a page with the text "It works!"... which appears
> to be untrue.
Thanks for letting us know, David!
James, heads up!
For now I committed the patch
On Wed, 18 Apr 2018, Martin Liška wrote:
> I would like to mention the attribute in GCC 8 changes.
Index: htdocs/gcc-8/changes.html
===
>
> New no_sanitize attribute has been added. The attribute
> on functions is used to
With HPE "integrating" SGI, ftp.sgi.com has gone away without a
replacement I could find, and I've also failed to find a potentially
new home for this document.
So I had to go ahead with the patch below; committed.
Gerald
Index: htdocs/readings.html
ards (from HEAD to 8, 8 to 7, and 7 to 6).
Gerald
2018-10-02 Gerald Pfeifer
* io/close.c [!HAVE_UNLINK_OPEN_FILE]: Include .
Index: libgfortran/io/close.c
===
--- libgfortran/io/close.c (revision 264772)
+++ libgfort
This just moved from http to https, and they put a redirect in place,
so pretty straightforward. Applied.
2018-10-01 Gerald Pfeifer
* doc/xml/manual/allocator.xml: Adjust link to "Reconsidering
Custom Memory Allocation".
Index: doc/xml/manual/all
This is a follow-up on the initial simplification I worked on this
morning, cf. https://gcc.gnu.org/ml/gcc-patches/2018-09/msg01782.html .
With this we no longer set the lang attribute to "en" via our global
style/MetaHTML pre-processing, but push lang="en" down into the
tags of all individual
I applied the patch below. Given a number of fixes in libstdc++/doc
I've applied recently, can one of you please regenerate the HTML pages
in the next days?
Thanks,
Gerald
2018-09-30 Gerald Pfeifer
* doc/xml/manual/messages.xml: Switch link to www.oracle.com
to https
The original link was simply broken, no redirect or anything, but
I'm relatively confident this is a good replacement.
Committed.
Gerald
2018-09-30 Gerald Pfeifer
* doc/xml/manual/policy_data_structures_biblio.xml: Update
link to Microsoft Component Model Object
...not just for "standard" pages, those that used to be XHTML and
are now HTML 5. On the way remove traces of XHTML around that,
which were still fine, but not necessary.
Committed.
Gerald
Index: style.mhtml
===
RCS file:
This removes the last traces of setting a DOCTYPE. All regular pages
now have this included directly and for install/ the conversion from
texinfo now does that.
David, this should be yet another change that'll help make your script
easier.
Committed.
Gerald
Index: style.mhtml
After my changes in the past weeks (and months) this is the last of
our regular, not automatically generated, pages that moves to HTML 5.
There are some further simplifications and cleanups on this page in
particular and our style sheet(s), but the majority of work is behind
us, and for those
Somehow this one apparently fell through when I made updates
in the last weeks.
Committed.
Gerald
Index: gcc-6/changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-6/changes.html,v
retrieving revision 1.107
diff -u -r1.107
The old link did not work any longer, without any redirect. This
seems to be a valid replacement.
Committed.
Gerald
Index: readings.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/readings.html,v
retrieving revision 1.302
diff -u
901 - 1000 of 3498 matches
Mail list logo
