Cumulative update of the OpenMP 5.x changes in GCC 12.
I hope it covers all essential changes. Of course,
some other could be added like 'omp target in_reduction',
which was missing before (oversight) and possibly other
things, which I have missed.
For the last bullet: the implementation-status
On Tue, Nov 09, 2021 at 02:04:09PM +, Jonathan Wakely wrote:
> OK for wwwdocs?
Sure, thanks.
> ---
> htdocs/projects/cxx-status.html | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/htdocs/projects/cxx-status.html b/htdocs/projects/cxx-status.htm
OK for wwwdocs?
---
htdocs/projects/cxx-status.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/projects/cxx-status.html b/htdocs/projects/cxx-status.html
index 0ff9e94d..d2d6eab4 100644
--- a/htdocs/projects/cxx-status.html
+++ b/htdocs/projects/cxx-status.html
Hi Thomas,
Am 07.11.21 um 19:18 schrieb Thomas Koenig via Fortran:
Hello world,
the attached patches fix the name of the function argument to CO_REDUCE
to conform to Fortran 2018 instead of the TR.
This is a user-visible change, so I have put this both into changes.html
and porting_to.html.
Hello world,
the attached patches fix the name of the function argument to CO_REDUCE
to conform to Fortran 2018 instead of the TR.
This is a user-visible change, so I have put this both into changes.html
and porting_to.html.
Regression-tested. OK for trunk?
Best regards
Thomas
Business as usual...
Gerald
---
htdocs/gcc-11/changes.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index 6dec8856..c81f0e82 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gcc-11/changes.html
@@ -142,7
This complements the same change I made to the GCC 5 release notes a bit
ago.
Gerald
---
htdocs/gcc-6/changes.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/gcc-6/changes.html b/htdocs/gcc-6/changes.html
index e95aabbe..6dd86d83 100644
---
nongnu.org has a permanent redirect (return code 301) to www.nongnu.org;
make that change on our end.
---
htdocs/gcc-4.7/changes.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/gcc-4.7/changes.html b/htdocs/gcc-4.7/changes.html
index dae1735d..21294cc3 100644
---
---
htdocs/gcc-5/changes.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/gcc-5/changes.html b/htdocs/gcc-5/changes.html
index 05e796dd..2e2e20e6 100644
--- a/htdocs/gcc-5/changes.html
+++ b/htdocs/gcc-5/changes.html
@@ -1084,7 +1084,7 @@ are not listed here).
Hi Sandra,
I've checked in the attached patch to announce the cleanup project that
Tobias and I have been working on over the last several months in the
GCC 12 release notes. I also updated the page for TS29113 on the GCC
wiki to reflect that anything that still doesn't work ought to be
I've checked in the attached patch to announce the cleanup project that
Tobias and I have been working on over the last several months in the
GCC 12 release notes. I also updated the page for TS29113 on the GCC
wiki to reflect that anything that still doesn't work ought to be
considered a
Adjust one of two links to classpath.org and avoid the other, by
removing the respective paragraph which is really not relevant any
longer.
---
htdocs/gcc-4.1/changes.html | 9 ++---
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git a/htdocs/gcc-4.1/changes.html
---
htdocs/git.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/git.html b/htdocs/git.html
index ac1f2eb9..881f1d38 100644
--- a/htdocs/git.html
+++ b/htdocs/git.html
@@ -334,7 +334,7 @@ in Git.
modula-2
This branch is for the
-
We've got a number of links to the DWARF standard on our page, which
requires some link maintenance. Remove this one for GCC 7 which is
unlikely to be used (much).
---
htdocs/gcc-7/changes.html | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/htdocs/gcc-7/changes.html
These two redirected from golang.org to pkg.go.dev.
---
htdocs/gcc-5/changes.html | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/htdocs/gcc-5/changes.html b/htdocs/gcc-5/changes.html
index a346c7f6..05e796dd 100644
--- a/htdocs/gcc-5/changes.html
+++
The www.dwarfstd.org webmasters suggested (via a redirect) to adjust
http links to https.
---
htdocs/gcc-4.7/changes.html | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/htdocs/gcc-4.7/changes.html b/htdocs/gcc-4.7/changes.html
index 5103e5ee..dae1735d 100644
---
---
htdocs/codingconventions.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/codingconventions.html b/htdocs/codingconventions.html
index 21cc95de..e4d30510 100644
--- a/htdocs/codingconventions.html
+++ b/htdocs/codingconventions.html
@@ -146,7 +146,7 @@ a large
Document the new __regio_symbol variable qualifier for PRU target.
Pushed.
Signed-off-by: Dimitar Dimitrov
---
htdocs/gcc-12/changes.html | 9 +
1 file changed, 9 insertions(+)
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 4f7bbd33..22839f2d 100644
---
Pushed. Jakub already added the feature test macros.
commit 78f03a4a633950743a416f5b9e7f721db7892090
Author: Marek Polacek
Date: Tue Oct 5 12:57:19 2021 -0400
cxx-status: Add papers from the October 2021 WG21 plenary
diff --git a/htdocs/projects/cxx-status.html
/changes.html b/htdocs/gcc-12/changes.html
index 45e87ea4..4f7bbd33 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -55,7 +55,7 @@ a work-in-progress.
The hppa[12] wwwdocs:*-*-hpux10* and
hppa[12]*-*-hpux11*
-configurations targeting 32bit PA-RISC with HP-UX
Just some editorial changes to simplify things.
Pushed.
Gerald
---
htdocs/gcc-12/changes.html | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 0e2962ee..45e87ea4 100644
--- a/htdocs/gcc-12/changes.html
+++
On Thu, 23 Sep 2021, liuhongt via Gcc-patches wrote:
> +IA-32/x86-64
> +
> + New ISA extension support for Intel AVX512-FP16 was added to GCC.
> + AVX512FP16 intrinsics are available via the -mavx512fp16
> + compiler switch.
> +
I think the support for _Float16 should be mentioned in
which are under the refs/dead/heads/* are of the Git repo.
> >
> >This moves them all to the "Inactive" or "Merged" section, as
> >appropriate.
> >
> >OK for wwwdocs?
>
> Ping
OK.
> >commit cbb29df7295bb49f957100e50939393b31e22433
> &
or "Merged" section, as
appropriate.
OK for wwwdocs?
Ping
commit cbb29df7295bb49f957100e50939393b31e22433
Author: Jonathan Wakely
Date: Thu Sep 16 12:20:15 2021 +0100
Move merged and inactive branches to the right section
diff --git a/htdocs/git.html b/htdocs/git.html
index 53267
---
htdocs/gcc-12/changes.html | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 81f62fe3..14149212 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -165,8 +165,12 @@ a
The https://gcc.gnu.org/git.html page is a total mess, listing dozens
and dozens of branches which haven't seen updates in a decade and
which are under the refs/dead/heads/* are of the Git repo.
This moves them all to the "Inactive" or "Merged" section, as
appropriate.
OK f
On Mon, Sep 06, 2021 at 03:20:44PM +0200, Tobias Burnus wrote:
> On 13.08.21 16:37, Tobias Burnus wrote:
>
> > Update the OpenMP section again, now that Jakub has added the 'masked'
> > construct.
> > Comments?
>
> Jakub did comment on IRC that it probably makes sense to do less
> frequent
On 13.08.21 16:37, Tobias Burnus wrote:
Update the OpenMP section again, now that Jakub has added the 'masked'
construct.
Comments?
Jakub did comment on IRC that it probably makes sense to do less
frequent commits.
Thus, I waited a while and now have an update list. Besides 'masked' it
now
On 8/30/21 12:54 PM, Tobias Burnus wrote:
> Document Roger's patch
> https://gcc.gnu.org/g:3c496e92d795a8fe5c527e3c5b5a6606669ae50d
>
> OK? Suggestions?
>
LGTM.
Thanks,
- Tom
Document Roger's patch
https://gcc.gnu.org/g:3c496e92d795a8fe5c527e3c5b5a6606669ae50d
OK? Suggestions?
Tobias
PS: I have a pending wwwdocs patch for OpenMP, but I think I will hold
off with an updated version until Jakub's next patch – to avoid too many
updates.
PPS: I also have a pending
TYPE_MODE of record and union depends on whether vector_mode_supported_p
returns true or not. x86-64 backend uses TYPE_MODE to decide how to pass
a parameter and return a value in a function. 64-bit integer vectors
were supported only by MMX and 64-bit float vector was supported only by
3DNOW.
Committed as obvious.
commit 6404392bcf74d2af7d171cc1df9b5c001d2218f8
Author: Jonathan Wakely
Date: Tue Aug 24 18:06:25 2021 +0100
Fix grammar in gcc-11 release notes
diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index b8bb2e69..6dec8856 100644
---
Pushed to wwwdocs as obvious.
commit 44d97225cc39f2cfbc3109c6a6473bde3886357a
Author: Jonathan Wakely
Date: Tue Aug 17 21:30:28 2021 +0100
Add missing punctuation to elements
diff --git a/htdocs/bugs/index.html b/htdocs/bugs/index.html
index 0a1b582a..99a1ddb1 100644
--- a/htdocs/bugs
g/pipermail/gcc-patches/2020-July/550102.html
>> "not suitable for mainline until the multiple-worker support is merged
>> there"
>>
>> @Andrew + @Julian: Do you intent to commit it relatively soon?
>> Regarding the wwwdocs patch, I can hol
ainline until the multiple-worker support is merged
> there"
>
> @Andrew + @Julian: Do you intent to commit it relatively soon?
> Regarding the wwwdocs patch, I can hold off until that commit or reword
> it to only cover the workers part.
Were these not part of the patch set Thomas was working on?
Andrew
Update the OpenMP section again, now that Jakub has added the 'masked'
construct.
Comments?
Tobias
-
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634
München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas
Heurung, Frank Thürauf;
Hi all,
On 19.07.21 17:28, Jakub Jelinek via Gcc-patches wrote:
On Mon, Jul 19, 2021 at 05:17:10PM +0200, Tobias Burnus wrote:
Update the OpenMP feature list.
Comments? Remarks?
I'd defer mentioning it until I actually finish it
With today's commits by Jakub, the implementation is rather
g/pipermail/gcc-patches/2020-July/550102.html
"not suitable for mainline until the multiple-worker support is merged
there"
@Andrew + @Julian: Do you intent to commit it relatively soon?
Regarding the wwwdocs patch, I can hold off until that commit or reword
it to only cover the
On Mon, 9 Aug 2021, Tobias Burnus wrote:
> Comments and/or suggestions?
Looks good from my perspective, with the feedback that Thomas
provided.
(Is "CU" a sufficiently established term, or might it make sense
to spell it out?)
Thanks,
Gerald
the feature does work ...)
ACK.
> Cf. also Andrew's talk of last year,
> https://linuxplumbersconf.org/event/7/contributions/749/attachments/560/988/AMD_GCN_Update_-_LPC_2020.pdf
> which I utilized when writing the attached wwwdocs patch.
>
> Comments and/or suggestions?
> gcc-12/
/contributions/749/attachments/560/988/AMD_GCN_Update_-_LPC_2020.pdf
which I utilized when writing the attached wwwdocs patch.
Comments and/or suggestions?
Tobias
-
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634
München; Gesellschaft mit beschränkter
it slightly clearer. Comparatively few users actually
> > use a self-built GCC based on official source tarballs, but that's OK.
> > Distro builds tend to be much closer to upstream these days, and we
> > rarely reject bug reports where the reporter is using a build from
> &g
On Jul 27, 2021, at 10:30 AM, Martin Sebor via Gcc-patches
wrote:
> On 7/27/21 9:16 AM, Jonathan Wakely via Gcc-patches wrote:
>> Secondly, releases are not issued by the GNU Project at all, they're
>> issued by the GCC release managers.
>
> I (and I suspect most users unfamiliar with the inner
ut that's OK.
Distro builds tend to be much closer to upstream these days, and we
rarely reject bug reports where the reporter is using a build from
Fedora, Ubuntu, Arch or whatever (unless it really is caused by a
downstream patch and doesn't reproduce with a gcc.gnu.org release).
OK for wwwdocs?
m these days, and we
rarely reject bug reports where the reporter is using a build from
Fedora, Ubuntu, Arch or whatever (unless it really is caused by a
downstream patch and doesn't reproduce with a gcc.gnu.org release).
OK for wwwdocs?
commit b7bf1f0b9f708673feeb13fcdbc1d461b82ad6d6
Author: J
I've now pushed this wwwdocs patch, which Gerald approved at
https://gcc.gnu.org/pipermail/gcc-patches/2021-June/572796.html
commit 0e4db42cddd88d2cc6780da884021284a10b9a4b
Author: Jonathan Wakely
Date: Tue Jul 27 16:04:42 2021 +0100
Remove FSF attribution from HTML page titles
diff
On Mon, 19 Jul 2021, Tobias Burnus wrote:
> Update the OpenMP feature list.
>
> Comments? Remarks?
I'd slightly tweak this
; so far, they can be specified on statements and
block-local variables, only.
to
. So far they can be specified on statements and
block-local variables.
On Mon, Jul 19, 2021 at 05:17:10PM +0200, Tobias Burnus wrote:
> Update the OpenMP feature list.
>
> Comments? Remarks?
I'd defer mentioning it until I actually finish it (hopefully later this
week or next week worst case).
> gcc-12/changes.html: OpenMP - mention C++11 attributes support
>
>
Update the OpenMP feature list.
Comments? Remarks?
Tobias
-
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634
München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas
Heurung, Frank Thürauf; Sitz der Gesellschaft: München;
Gerald Pfeifer writes:
>> +is fully operational with the GCC 10 and GCC 11 (on
>
> Here I'd omit "the", though I cannot (linguistically) explain why
> and have to refer to established practice.
thanks for catching the unnecessary "the" - all committed and pushed
now,
regards,
Gaius
On Mon, 12 Jul 2021, Gaius Mulley wrote:
>> Usually I'd just say "subject", which is a header in our mail systems;
>> the term "subject line" isn't widely used.
> feel free to overrule and use "subject". I copied the text from other
> branch descriptions :-) (there are 38 uses). I guess there
Gerald Pfeifer writes:
> I realize this predates your patch (which merely changes version numbers),
> but a reference to back ends could be misunderstood. I assume GNU Modula-2
> doesn't just use the back ends (x86, aarch64,...), but also the middle-end
> and tree optimizers etc.?
>
> What do
Hi Gaius,
On Thu, 8 Jul 2021, Gaius Mulley wrote:
> Here are two proposed patches to wwwdocs:
thank you for thinking of updating the web pages, too!
> diff --git a/htdocs/frontends.html b/htdocs/frontends.html
:
> http://www.nongnu.org/gm2/;>GNU Modula-2 implements
> the P
Hello Gerald,
Here are two proposed patches to wwwdocs:
htdocs/frontends.html: Update the description of GNU Modula-2.
htdocs/git.html: Document the new devel/modula-2 branch.
regards,
Gaius
=
diff --git a/htdocs/frontends.html b/htdocs/frontends.html
index bec33b7b..60f08aa4
Now committed as 5c17042e880a5d1a3eb261f73e1b9da0c1aa2641
https://gcc.gnu.org/gcc-12/changes.html
Tobias
On 29.06.21 18:38, Julian Brown wrote:
On Tue, 29 Jun 2021 17:34:00 +0200
Tobias Burnus wrote:
This documents AMD GCN's new much-more complete TI-mode
(__int128_t) support, that was as
On Tue, 29 Jun 2021 17:34:00 +0200
Tobias Burnus wrote:
> This documents AMD GCN's new much-more complete TI-mode
> (__int128_t) support, that was as v2 just posted by Julian
> and should get committed very soon.
Thank you!
> gcc-12/changes.html: GCN - add TI mode, mention -foffload(-options)
This documents AMD GCN's new much-more complete TI-mode
(__int128_t) support, that was as v2 just posted by Julian
and should get committed very soon.
Additionally, -foffload= (previously undocumented) has been
split into -foffload= and -foffload-options= and now has a
documentation. Hence, both
On 23.06.21 11:58, Andrew Stubbs wrote:
On 23/06/2021 10:53, Tobias Burnus wrote:
+ additionally the following features which were available in C
and C++
+ before: depobj, mutexinoutset and
I realise that you did not invent this awkward wording, but I'd prefer
...
"the following
It's been a minute since I've updated our C++ DR table, so this patch
adds news DRs. I've also written a script that check each DR's status
against the upstream document. That revealed that many entries in our
table were out of sync, so I've gone through all of them and fixed them.
I've also
On 23/06/2021 10:53, Tobias Burnus wrote:
+ additionally the following features which were available in C and C++
+ before: depobj, mutexinoutset and
I realise that you did not invent this awkward wording, but I'd prefer ...
"the following features that were previously only
Hi all,
this patch updates OpenMP for the non-bug-fix commits which have
been done in the last weeks.
It also updates GCN. The change assumes that the just approved
patch is committed ...
Comments, thoughts, wording suggestions? Did I miss some commit/feature?
Tobias
-
Mentor
On Tue, Jun 22, 2021 at 02:38:46PM -0400, Jason Merrill wrote:
> On 6/22/21 1:14 PM, Marek Polacek wrote:
> > P1847 has always been "implemented" as the paper says.
> > P2186 needs a few libstdc++ changes that Jonathan already implemented.
>
> I figured these removals didn't need to be called out
On 6/22/21 1:14 PM, Marek Polacek wrote:
P1847 has always been "implemented" as the paper says.
P2186 needs a few libstdc++ changes that Jonathan already implemented.
I figured these removals didn't need to be called out in the table, but
it's also fine to have them.
commit
It's time to start adding new C++ features.
Pushed.
commit e373348138d8d767067c0a79b3ddc6a70cbee3a4
Author: Marek Polacek
Date: Tue Jun 22 13:19:37 2021 -0400
gcc-12/changes.html: Add if consteval
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index
P1847 has always been "implemented" as the paper says.
P2186 needs a few libstdc++ changes that Jonathan already implemented.
Pushed.
commit 7b804041d34c344a190105e78c6058e2645bf7cb
Author: Marek Polacek
Date: Tue Jun 22 13:10:41 2021 -0400
cxx-status: Add more C++23 proposals
diff
Pushed.
Gerald
---
htdocs/mirrors.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/mirrors.html b/htdocs/mirrors.html
index 083c6c04..75c71b95 100644
--- a/htdocs/mirrors.html
+++ b/htdocs/mirrors.html
@@ -35,7 +35,7 @@ mirrors. The following sites mirror the
On 6/15/21 3:39 AM, Jonathan Wakely wrote:
On Tue, 15 Jun 2021 at 01:12, Martin Sebor wrote:
On 6/14/21 10:25 AM, Jonathan Wakely via Gcc-patches wrote:
I think this is an improvement on the current structure of the docs,
but I'd like to hear what others think.
The text looks more detailed
On Tue, Jun 15, 2021 at 05:04:51PM +0200, Jakub Jelinek wrote:
> On Tue, Jun 15, 2021 at 09:24:44AM -0500, Segher Boessenkool wrote:
> > IMNSHO this all should emphasise *why* these things are recommended, and
> > don't pretend these are "rules" at all. They are not. The important
>
> Many of
On Tue, Jun 15, 2021 at 09:24:44AM -0500, Segher Boessenkool wrote:
> IMNSHO this all should emphasise *why* these things are recommended, and
> don't pretend these are "rules" at all. They are not. The important
Many of them actually are rules.
Everything that is verified by the pre-commit
On Tue, 15 Jun 2021 at 15:25, Segher Boessenkool wrote:
> > Again, you're objecting to the current text:
> > https://gcc.gnu.org/contribute.html#patches
>
> Not at all, there are + in front, this is proposed new text.
Moved from one file to another.
>
> > > IMNSHO this all should emphasise *why*
t anything about commit format for the
> > > wwwdocs repo. Should the "wwwdocs" be a classifier (as in this email)
> > > or a component tag?
> >
> > I use proper components for wwwdocs as well, and when I send the patch
> > to gcc-patches@ I replace the [PATCH] by [www
On Tue, 15 Jun 2021 at 14:03, Segher Boessenkool wrote:
>
> On Mon, Jun 14, 2021 at 05:25:56PM +0100, Jonathan Wakely via Gcc-patches
> wrote:
> > We don't currently say document anything about commit format for the
> > wwwdocs repo. Should the "wwwdocs" be
On Tue, Jun 15, 2021 at 10:39:58AM +0100, Jonathan Wakely via Gcc-patches wrote:
> I think suggesting a single format (but allowing variations on it) is
> **much** better than not saying anything at all. For new contributors
> it's helpful to say "this is what we want" so they have a guideline to
On Thu, 3 Jun 2021, Jonathan Wakely wrote:
> An alternative change would be to just drop the mention of the FSF
:
> And as I pointed out previously, none of these sites refer to the FSF
> in their page s:
>
> https://www.gnu.org/software/gdb/
> https://www.gnu.org/software/libc/
>
On Mon, Jun 14, 2021 at 06:12:24PM -0600, Martin Sebor via Gcc-patches wrote:
> The text looks more detailed and arguably more accurate but also
> makes it sound more complicated and rigid than necessary.
+1
> (why ask for no space and not, for example PR #n?)
Because it is shorter. If
On Tue, Jun 15, 2021 at 10:30:05AM +0100, Jonathan Wakely via Gcc-patches wrote:
> Slightly improved version, moving the "this highlights to the relevant
> maintainers that the patch might need their attention" back to the
> patch email docs, and adding rationale for good one-line subjects.
Ah,
On Mon, Jun 14, 2021 at 05:25:56PM +0100, Jonathan Wakely via Gcc-patches wrote:
> We don't currently say document anything about commit format for the
> wwwdocs repo. Should the "wwwdocs" be a classifier (as in this email)
> or a component tag?
I use proper components
On Tue, 15 Jun 2021 at 01:12, Martin Sebor wrote:
>
> On 6/14/21 10:25 AM, Jonathan Wakely via Gcc-patches wrote:
> > I think this is an improvement on the current structure of the docs,
> > but I'd like to hear what others think.
>
> The text looks more detailed and arguably more accurate but
On 14/06/21 17:25 +0100, Jonathan Wakely wrote:
I think this is an improvement on the current structure of the docs,
but I'd like to hear what others think.
Slightly improved version, moving the "this highlights to the relevant
maintainers that the patch might need their attention" back to the
about commit format for the
wwwdocs repo. Should the "wwwdocs" be a classifier (as in this email)
or a component tag?
On Mon, Jun 14, 2021 at 09:56:12AM +0200, Gerald Pfeifer wrote:
> On Sun, 13 Jun 2021, Dimitar Dimitrov wrote:
> >> TI's server has been telling us that "The PRU-ICSS wiki is in the
> >> process of being migrated to software-dl.ti.com" for five months.
> >> Time to pull the plug.
> > Could you
Hi Gerald:
Thanks your patch, my grammar is really...weak :p
Hi Bernhard:
>> + Add new option -misa-spec=* to control ISA spec version.
>> + This controls the default version of each extensions.
>> + It defaults to 2.2.
> Is "each extensions" in plural really correct gramatically?
>
I think this is an improvement on the current structure of the docs,
but I'd like to hear what others think.
We don't currently say document anything about commit format for the
wwwdocs repo. Should the "wwwdocs" be a classifier (as in this email)
or a component tag
On Sun, 13 Jun 2021, Dimitar Dimitrov wrote:
>> TI's server has been telling us that "The PRU-ICSS wiki is in the
>> process of being migrated to software-dl.ti.com" for five months.
>> Time to pull the plug.
> Could you please consider the following replacement?
>
On Sun, 13 Jun 2021, Bernhard Reutner-Fischer wrote:
>> + Add new option -misa-spec=* to control ISA spec version.
>> + This controls the default version of each extensions.
>> + It defaults to 2.2.
> Is "each extensions" in plural really correct gramatically?
> "default version of
On Mon, May 31, 2021 at 12:20:21AM +0200, Gerald Pfeifer wrote:
> TI's server has been telling us that "The PRU-ICSS wiki is in the
> process of being migrated to software-dl.ti.com" for five months.
> Time to pull the plug.
> ---
> htdocs/readings.html | 1 -
> 1 file changed, 1 deletion(-)
>
>
On Sun, 13 Jun 2021 07:58:50 +0200 (CEST)
Gerald Pfeifer wrote:
> RISC-V has received a very nice section in the GCC 11 release notes
> thanks to Kito.
>
> This are a couple of editorial changes, completing some sentence and
> breaking longer sentences among others, and a bit of grammar.
>
>
RISC-V has received a very nice section in the GCC 11 release notes
thanks to Kito.
This are a couple of editorial changes, completing some sentence and
breaking longer sentences among others, and a bit of grammar.
Pushed.
Gerald
---
htdocs/gcc-11/changes.html | 33
On Mon, 7 Jun 2021, Jonathan Wakely wrote:
> This adds id attributes to the heading elements of
> https://gcc.gnu.org/gcc-5/porting_to.html (so that I can link directly
> to the section on inline functions).
>
> All later porting_to.html notes have anchors like this.
>
This adds id attributes to the heading elements of
https://gcc.gnu.org/gcc-5/porting_to.html (so that I can link directly
to the section on inline functions).
All later porting_to.html notes have anchors like this.
OK for wwwdocs?
commit 9f1723bc1d6b52fcfcfc4a8aee93eada98412e78
Author
This should have been in the GCC 11 release notes, pushed now.
commit bbbf05e7f3d3e7a74d23e8cc252ebae895158abe
Author: Jonathan Wakely
Date: Mon Jun 7 10:27:00 2021 +0100
Document libstdc++ support for generic unordered lookup
diff --git a/htdocs/gcc-11/changes.html
On Wed, 2 Jun 2021, Gerald Pfeifer wrote:
> On Tue, 1 Jun 2021, Segher Boessenkool wrote:
> > We haven't had Sender: for a while now.
>
> "a while now" was about four(?) hours when you sent that yesterday. :-)
>
> I know since I still had been using that and was looking for all my
> missing
by the GCC developers and aided by
the steering committee.
OK for wwwdocs?
An alternative change would be to just drop the mention of the FSF,
since they don't fund GCC or provide hosting etc., as in the attached
patch.
And as I pointed out previously, none of these sites refer to the FSF
in th
ittee.
OK for wwwdocs?
commit d157082f49725510560cb83f2f1c045e2968ad3b
Author: Jonathan Wakely
Date: Sun Apr 18 23:42:26 2021 +0100
Do not rewrite the page titles
Remove GNU and FSF attribution from HTML page titles.
diff --git a/htdocs/style.mhtml b/htdocs/style.mhtml
inde
With TI official wiki gone, let's put stable links to their proprietary
toolchain documents, which happen to describe ABI and instruction set.
Signed-off-by: Dimitar Dimitrov
---
htdocs/readings.html | 2 ++
1 file changed, 2 insertions(+)
diff --git a/htdocs/readings.html
On Wed, Jun 02, 2021 at 10:25:34AM +0200, Andreas Schwab wrote:
> On Jun 01 2021, Segher Boessenkool wrote:
> > -* ^List-Id: .*<.*@gcc.gnu.org>$
> > +* ^List-Id: .*<.*.gcc.gnu.org>$
>
> Shouldn't the < and > be mangled as and ?
"It works fine for me!"
You are right of course.
Segher
tness elsewhere (it now will match any list id that
has the string gccXgnuYorg anywhere in it, where X and Y can be any
character).
> Or ^List-Id: .*gcc(-announce|-patches|-cvs-wwwdocs)?.gcc.gnu.org in
> one case.
>
> What do you think?
I only filter "gcc", "gcc-p
On Wed, Jun 02, 2021 at 10:44:34AM +0200, Gerald Pfeifer wrote:
> On Tue, 1 Jun 2021, Segher Boessenkool wrote:
> > We haven't had Sender: for a while now.
>
> "a while now" was about four(?) hours when you sent that yesterday. :-)
Ah, I thought it was since we moved to the new mailing list
On Tue, 1 Jun 2021, Segher Boessenkool wrote:
> We haven't had Sender: for a while now.
"a while now" was about four(?) hours when you sent that yesterday. :-)
I know since I still had been using that and was looking for all my
missing gcc-related mails yesterday afternoon. Thanks for spotting
On Jun 01 2021, Segher Boessenkool wrote:
> diff --git a/htdocs/lists.html b/htdocs/lists.html
> index 4ac5d5a84cd1..e9636198b732 100644
> --- a/htdocs/lists.html
> +++ b/htdocs/lists.html
> @@ -226,7 +226,7 @@ our lists into a single folder named INLIST.gcc:
>
>
> :0
> -* ^List-Id:
801 - 900 of 3820 matches
Mail list logo