On Fri, May 27, 2022 at 09:41:22AM +0200, Tobias Burnus wrote:
> On 25.05.22 17:55, Tobias Burnus wrote:
> > I had a look at the OpenMP 5.2 changes and found some more,
> > which I think should be listed. Some were rather hidden, two
> > were only documented in the deprecate part.
>
> Fixes: Remov
On 25.05.22 17:55, Tobias Burnus wrote:
I had a look at the OpenMP 5.2 changes and found some more,
which I think should be listed. Some were rather hidden, two
were only documented in the deprecate part.
Fixes: Remove the last two items – they were already in the list (ups).
libgomp/libgomp.t
On Tue, 24 May 2022, Marek Polacek via Gcc-patches wrote:
> > And cases where some support in GCC should
> > definitely be done to consider the feature implemented, even when not
> > needed for conformance (e.g. the %wN, %wfN printf/scanf formats need
> > implementing in glibc, and correspondin
I had a look at the OpenMP 5.2 changes and found some more,
which I think should be listed. Some were rather hidden, two
were only documented in the deprecate part.
I also added the 'begin declare target', which is a variant
to the delimited form of 'declare target' – the non-begin
variant is the
On 25/05/2022 12:16, Tobias Burnus wrote:
On 25.05.22 11:18, Andrew Stubbs wrote:
On 24/05/2022 17:44, Tobias Burnus wrote:
On 24.05.22 17:31, Andrew Stubbs wrote:
amdgcn: Add gfx90a support
I've deliberately avoided the MI100 and MI200 names because they're
really not that simple. MI100 is g
On 25.05.22 11:18, Andrew Stubbs wrote:
On 24/05/2022 17:44, Tobias Burnus wrote:
On 24.05.22 17:31, Andrew Stubbs wrote:
amdgcn: Add gfx90a support
I've deliberately avoided the MI100 and MI200 names because they're
really not that simple. MI100 is gfx908, but MI150 is gfx906 and MI125
is gfx
On 24/05/2022 17:44, Tobias Burnus wrote:
On 24.05.22 17:31, Andrew Stubbs wrote:
amdgcn: Add gfx90a support
Attached is an attempt to update invoke.texi
I've deliberately avoided the MI100 and MI200 names because they're
really not that simple. MI100 is gfx908, but MI150 is gfx906 and MI12
On Tue, May 24, 2022 at 06:11:09PM +, Joseph Myers wrote:
> On Tue, 24 May 2022, Marek Polacek via Gcc-patches wrote:
>
> > I thought it'd be nice to have a table that documents our C support
> > status, like we have https://gcc.gnu.org/projects/cxx-status.html for C++.
> > We have https://gcc
On Tue, 24 May 2022, Marek Polacek via Gcc-patches wrote:
> +
This actually looks like a mix of papers approved at the Oct 2020 meeting
and those approved at the Nov/Dec 2020 meeting, though I haven't checked
the lists in detail against those the minutes show as being approved as-is
or wit
On 5/24/22 16:33, Gerald Pfeifer wrote:
> Hi Martin,
>
> On Tue, 24 May 2022, Martin Liška wrote:
>> +AddressSanitizer defaults to
>> detect_stack_use_after_return=1 on Linux target.
>
> did you mean targets, or really just target?
>
> (And Linux or GNU/Linux, though that one is more disput
On Tue, 24 May 2022, Marek Polacek via Gcc-patches wrote:
> I thought it'd be nice to have a table that documents our C support
> status, like we have https://gcc.gnu.org/projects/cxx-status.html for C++.
> We have https://gcc.gnu.org/c99status.html, but that's C99 only.
>
> So here's a patch to
I thought it'd be nice to have a table that documents our C support
status, like we have https://gcc.gnu.org/projects/cxx-status.html for C++.
We have https://gcc.gnu.org/c99status.html, but that's C99 only.
So here's a patch to add just that. For C99, I used c99status.html but
added paper number
where to use it, but reads much worse. – Pick one or suggest a better
one.
[wwwdocs, only]: Actually, regarding the gcc-13/changes, I am wondering
whether the best choice is to use the first wording but link to the
-march= page. That's what the new variant now does – see attachment.
(The link
On 24.05.22 17:31, Andrew Stubbs wrote:
amdgcn: Add gfx90a support
Attached is an attempt to update invoke.texi
And to update the gcc-13/changes.html. Regarding the latter, I have to
versions – the first is more readable, the latter makes more clear where
to use it, but reads much worse. – Pic
Hi Martin,
On Tue, 24 May 2022, Martin Liška wrote:
> +AddressSanitizer defaults to
> detect_stack_use_after_return=1 on Linux target.
did you mean targets, or really just target?
(And Linux or GNU/Linux, though that one is more disputed, I know.
Just following our own coding conventions...
On Tue, May 24, 2022 at 8:42 AM Martin Liška wrote:
>
> Ready to be installed?
>
> Thanks,
> Martin
>
> ---
> htdocs/gcc-13/changes.html | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
> index 6c5b2a37..f7f6866d 100644
> --- a/ht
Ready to be installed?
Thanks,
Martin
---
htdocs/gcc-13/changes.html | 3 +++
1 file changed, 3 insertions(+)
diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index 6c5b2a37..f7f6866d 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -47,6 +47,9 @@
Pushed to wwwdocs.
commit f55f35c86c68143a2b148c66e4b0b560c852ce6f
Author: Jonathan Wakely
Date: Tue May 24 13:06:11 2022 +0100
Document changes in libstdc++
diff --git a/htdocs/gcc-13/porting_to.html b/htdocs/gcc-13/porting_to.html
index b3e0895a..84a00f21 100644
--- a/htdocs/gcc-13
Thank you, Gerald :)
On Sun, May 22, 2022 at 6:29 AM Gerald Pfeifer wrote:
>
> I'm not sure when that sneaked in (and it predates that last entry),
> but followed by is one too many in any case. :-)
>
> Pushed.
>
> Gerald
> ---
> htdocs/gcc-12/changes.html | 1 -
> 1 file changed, 1 deletion(-
I'm not sure when that sneaked in (and it predates that last entry),
but followed by is one too many in any case. :-)
Pushed.
Gerald
---
htdocs/gcc-12/changes.html | 1 -
1 file changed, 1 deletion(-)
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 3b94378e..ae03c3c
On Wed, 11 May 2022, Kito Cheng via Gcc-patches wrote:
> LGTM, I think document what we really did in GCC 12 is never too late :P
Totally. And thanks for doing this, Palmer.
I went ahead and made two editorial changes per the patch below
which I pushed.
Gerald
commit 87fb03bc6ce3e190ba74215a9aa
On Thu, May 19, 2022 at 02:13:03PM +0200, Tobias Burnus wrote:
> Hi Jakub, hi all,
>
> the main reason for this patch is to change Documentation from to
> in projects/gomp/ as I realized that those cross references weren't as
> prominently visible as I had hoped for.
>
> Additionally:
> * gcc-1
Hi Jakub, hi all,
the main reason for this patch is to change Documentation from to
in projects/gomp/ as I realized that those cross references weren't as
prominently visible as I had hoped for.
Additionally:
* gcc-13/changes.html: Add a feature I had missed (non-rect loop nest in F90)
+ new
On Tue, May 17, 2022 at 11:50:15AM +0200, Tobias Burnus wrote:
> On 17.05.22 11:00, Jakub Jelinek wrote:
> > BTW, it would be really nice to use colors like
> > https://gcc.gnu.org/projects/cxx-status.html uses, use just GCC versions
> > instead of GCC version and No instead of N and use hyperlinks
On 17.05.22 11:00, Jakub Jelinek wrote:
BTW, it would be really nice to use colors like
https://gcc.gnu.org/projects/cxx-status.html uses, use just GCC versions
instead of GCC version and No instead of N and use hyperlinks to
changes.html OpenMP ids (or just changes.html if we don't have an id).
On Tue, May 17, 2022 at 10:49:42AM +0200, Tobias Burnus wrote:
> Thoughts on this part?
Either place is fine.
> > > +Map-order clarificationsGCC?
> > This entry I gave up on, it isn't exactly clear to me what that
> > bullet is about and once we figure that out, we need to do some archeology
> >
Hi Jakub & Gerald,
first, thanks for all the suggestions!
I have now followed Gerald's suggestion to place the table into the main
GOMP page.
I then also decided to make it more GCC-user orientated than
GCC-developer orientated by re-writing the intro (but keeping the old
one as background), al
On Mon, May 16, 2022 at 11:42:03AM +0200, Tobias Burnus wrote:
> small update (interdiff): s/s/S/ for consistency, missed one GCC 13 commit,
> and
> improved wording of the enter/exit change. (New wording better captures the
> effect; I was thinking too much of the changed spec wording not of the
On Mon, 16 May 2022, Tobias Burnus wrote:
> PPS: I think we should consider to further cleanup/consolidate both the
> generic gomp landing page and the http://gcc.gnu.org/wiki/openmp wiki.
> Current the information is too far spread and too difficult to find.
Yes, that sounds like a great idea, to
The validator would not have caught this - `grep -r` rules. :-)
Gerald
---
htdocs/gcc-13/changes.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index f21b546b..a1b64df3 100644
--- a/htdocs/gcc-13/changes.html
+++ b
On Sat, 14 May 2022, Jakub Jelinek wrote:
> I often just copy from git diff from a year ago, which has the
> disadvantages that issues that are fixed later on keep reappearing.
Ah, makes sense. ;-)
Any idea how we/I might help avoid or mitigate this? (Even a validator
would not catch all, as I ju
Hi Tobias,
On Sat, 14 May 2022, Tobias Burnus wrote:
> Jakub and I discussed the other day that it would be useful
> to have a page similar to
> https://gcc.gnu.org/projects/cxx-status.html
> to provide by-GCC-version information of the which OpenMP are supported.
this looks like a great idea,
Hi all,
small update (interdiff): s/s/S/ for consistency, missed one GCC 13 commit, and
improved wording of the enter/exit change. (New wording better captures the
effect; I was thinking too much of the changed spec wording not of the effective
result.)
Plus added some cross-ref hyperlinks to mak
Jakub and I discussed the other day that it would be useful
to have a page similar to
https://gcc.gnu.org/projects/cxx-status.html
to provide by-GCC-version information of the which OpenMP are supported.
The list is based on
* https://gcc.gnu.org/onlinedocs/libgomp/OpenMP-Implementation-Status.
On Sat, May 14, 2022 at 02:12:06PM +0200, Gerald Pfeifer wrote:
> I pushed this minor update on top of the GCC 12 release changes.
>
> Jakub, I believe you have been using somewhere else,
> too. Not a biggie, and nothing to do. I'll take care...
I often just copy from git diff from a year ago, w
I pushed this minor update on top of the GCC 12 release changes.
Jakub, I believe you have been using somewhere else,
too. Not a biggie, and nothing to do. I'll take care...
Gerald
here came in via e9d81288aaae7626d7b511e0f84cba3e72f47b52
which is deprecated. Simply use an id instead.
---
ht
On Sat, 7 May 2022, Gerald Pfeifer wrote:
>> +LoongArch
> Okay, thanks.
And here is a markup fix on top, which I just pushed.
Gerald
commit 01a1afc13afd0e2b981262b0a1bf9ba1d7d19f79
Author: Gerald Pfeifer
Date: Sat May 14 00:27:52 2022 +0200
gcc-12: Fix markup in the Loongson section
di
On Tue, 10 May 2022 18:34:33 PDT (-0700), Kito Cheng wrote:
LGTM, I think document what we really did in GCC 12 is never too late :P
OK, committed.
On Fri, Apr 29, 2022 at 2:23 AM Palmer Dabbelt wrote:
---
IMO this one is worth documenting too, not sure if it's too late for
gcc-12's doc
On Wed, 6 Apr 2022, Xi Ruoyao via Gcc-patches wrote:
> Document ABI changes in r12-7961, 7962, and 8023. Ok for wwwdocs?
Thank you!
Note is deprecated, and we generally use id= attributes.
I made this change, and also expanded the anchor from just "ABI" which
is very generic to
This is a minor follow-up to Martin's patch
commit 6b788fa278b4f863a17ab80e0bf4991c3d8de167
Author: Martin Liska
Date: Mon Apr 19 14:55:54 2021 +0200
Move branch_changer.py usage to branching.html.
though the markup predates his change (which merely made me notice it).
Pushed.
Ger
LGTM, I think document what we really did in GCC 12 is never too late :P
On Fri, Apr 29, 2022 at 2:23 AM Palmer Dabbelt wrote:
>
> ---
> IMO this one is worth documenting too, not sure if it's too late for
> gcc-12's docs (due to those branch commits) so I haven't committed it
> yet to avoid an
Hi Gerald,
Thinks for your review. As your suggestion, change the HTML ids to
lowercase. And pushed.
Thanks.
Chenghua
On 5/7/22 22:38, Gerald Pfeifer wrote:
On Sat, 7 May 2022, xucheng...@loongson.cn wrote:
+LoongArch
I usually recommend all lowercase for HTML ids. That is only a
recomme
On Sat, 7 May 2022, xucheng...@loongson.cn wrote:
> +LoongArch
I usually recommend all lowercase for HTML ids. That is only a
recommendation, though, and if you strongly prefer "LoongArch"
over "loong" or "loongarch" that is fine.
Okay, thanks.
Gerald
From: Chenghua Xu
---
htdocs/gcc-12/changes.html | 13 +
1 file changed, 13 insertions(+)
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index c64827bd..995a1a42 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -695,6 +695,19 @@ funct
Hi!
Right in time for the GCC 12.1 release -- yay \o/ -- I've pushed
to wwwdocs commit c6a7f816f3531d5727674620d74818fe1d150467
"GCC 12: OpenACC", see attached.
Online: <https://gcc.gnu.org/gcc-12/changes.html#openacc>.
Grüße
Thomas
-
Siemens Electronic D
Hi,
I just pushed the attached patch to update the mail links and dates for
GCC 12 and GCC 13, as simple and obvious.
Regards
Thomasdiff --git a/htdocs/index.html b/htdocs/index.html
index 199181b1..e1bb584e 100644
--- a/htdocs/index.html
+++ b/htdocs/index.html
@@ -172,7 +172,7 @@ Mor
Hi,
after noticing an error in the gcc12 changes.html file, I fixed it as
obvious and simple with the attached patch.
Best regards
Thomas
Sun May 1 00:05:10 2022 +0200
Added equals sign to fix broken link in RISC-V section.
* gcc-12/changes.html: Fixed broken link.
dif
Hi Mikael,
OK in any case. Anything is better than nothing.
Here is what I committed, with one final tweak.
Thanks!
Best regards
Thomas
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -501,6 +501,15 @@ function Multiply (S1, S2 : Sign) return Sign is
conf
Le 29/04/2022 à 22:10, Thomas Koenig via Fortran a écrit :
the attached patch documents the support for IEEE long double for
Fortran. OK? Suggestions for better wording?
I'd like to get this in before the gcc12 release. It would also
qualify as obviously correct, I think :-) so I'll commit
the attached patch documents the support for IEEE long double for
Fortran. OK? Suggestions for better wording?
I'd like to get this in before the gcc12 release. It would also
qualify as obviously correct, I think :-) so I'll commit this
on Sunday unless there are any objections.
Patch at
On Thu, Apr 28, 2022 at 7:30 PM Xi Ruoyao via Gcc-patches
wrote:
>
> Ping.
OK.
> On Wed, 2022-04-06 at 23:26 +0800, Xi Ruoyao via Gcc-patches wrote:
> > Document ABI changes in r12-7961, 7962, and 8023. Ok for wwwdocs?
> >
> > ---
> >
---
IMO this one is worth documenting too, not sure if it's too late for
gcc-12's docs (due to those branch commits) so I haven't committed it
yet to avoid any fallout.
---
htdocs/gcc-12/changes.html | 3 +++
1 file changed, 3 insertions(+)
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/
Ping.
On Wed, 2022-04-06 at 23:26 +0800, Xi Ruoyao via Gcc-patches wrote:
> Document ABI changes in r12-7961, 7962, and 8023. Ok for wwwdocs?
>
> ---
> htdocs/gcc-12/changes.html | 25 -
> 1 file changed, 24 insertions(+), 1 deletion(-)
>
> diff
Hi,
the attached patch documents the support for IEEE long double for
Fortran. OK? Suggestions for better wording?
Best regards
Thomas
Mention support for IEEE 128-bit long double for Fortran.
* htdocs/gcc-12/changes.html: Mention support for IEEE
128-bit long doubl
---
htdocs/gcc-12/changes.html | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 78b7b05f..e9f132c0 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -736,7 +736,18 @@ function M
Pushed to wwwdocs.
---
htdocs/gcc-12/changes.html | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 4f904bfd..78b7b05f 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -467,11 +467,13
Pushed.
Gerald
---
htdocs/frontends.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/frontends.html b/htdocs/frontends.html
index 748ca182..3aa06bbb 100644
--- a/htdocs/frontends.html
+++ b/htdocs/frontends.html
@@ -29,7 +29,7 @@ are very mature.
-http://www.g
On Fri, 15 Apr 2022, Fernando Oleo Blanco wrote:
> thank you for your comments. As you have picked up, HTML is not my
> strongest language.
>
> I did not know that "<" and ">" had to scaped in HTML, I will try to
> remember that.
No worries, Fernando. "<" and ">" require special handling in HTML
On Wed, 13 Apr 2022, Gerald Pfeifer wrote:
> I am not familiar with that Emacs mode, but < and > are special characters
> in HTML and have to be written as < (less than) and > (greater than)
> respectively.
Here is a second batch which I had missed originally.
Also pushed...
Gerald
commit a
Am Wed, 13 Apr 2022 23:04:17 -0600 (MDT)
schrieb "Gerald Pfeifer" :
> On Wed, 13 Apr 2022, Gerald Pfeifer wrote:
> > This is the first batch of fixes. Pushed.
>
> Hmm, there is one issue that confused me a bit. What did you want to
> relay by the following?
>
>+Pattern matching
>+
On 05/04/22 06:05 +, Arnaud Charlet wrote:
Thank you for the feedback. Should I remove it and resuply the patch or
can you/GCC maintainers do the modification before merging?
Can you please resubmit it?
I'll let others comment on the need to sign a contributor agreement, my
understanding i
On Wed, 13 Apr 2022, Gerald Pfeifer wrote:
> This is the first batch of fixes. Pushed.
Hmm, there is one issue that confused me a bit. What did you want to
relay by the following?
+Pattern matching
+
+ The case statement has been extended to cover
Currently that is a withi
On Mon, 4 Apr 2022, Fernando Oleo Blanco via Gcc-patches wrote:
> this is my first patch to GCC, if there is anything off, please, say
> so. I have used the default HTML formatting that comes with Emacs.
I am not familiar with that Emacs mode, but < and > are special characters
in HTML and have t
I've pushed the following release notes change to the GCC website:
https://gcc.gnu.org/gcc-12/changes.html#jit
covering the 5 patches from Antoni that I pushed yesterday.
Dave
---
htdocs/gcc-12/changes.html | 22 +-
1 file changed, 21 insertions(+), 1 deletion(-)
diff --gi
On Tue, 2022-04-12 at 10:03 -0400, David Malcolm wrote:
> I've pushed the following change to the website, covering -fanalyzer
> changes in GCC 12.
(sorry, forgot to put wwwdocs in the subject)
>
> ---
> htdocs/gcc-12/changes.html | 115
>
Gerald Pfeifer writes:
> I pushed this for now.
>
> Gaius, if you want to make changes to that section of readings.html,
> absolutely be free doing so (and I'll be happy help, too).
>
> Gerald
>
> ---
> htdocs/readings.html | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/htdocs/readings.
> Thank you all for your feedback and guidance. I have taken Eric's
> feedback and deleted the relevant entry.
>
> Since I do not have write access, I cannot add myself to the
> MAINTAINERS file. Therefore, I want to explicitly state that I am
> submitting these patches under the DCO. I have read
I pushed this for now.
Gaius, if you want to make changes to that section of readings.html,
absolutely be free doing so (and I'll be happy help, too).
Gerald
---
htdocs/readings.html | 1 -
1 file changed, 1 deletion(-)
diff --git a/htdocs/readings.html b/htdocs/readings.html
index 12755d7e..8
Pushed.
Gerald
---
htdocs/contribute.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/contribute.html b/htdocs/contribute.html
index c0223738..c985b87d 100644
--- a/htdocs/contribute.html
+++ b/htdocs/contribute.html
@@ -145,7 +145,7 @@ eliminate them all.
Web Site
Document ABI changes in r12-7961, 7962, and 8023. Ok for wwwdocs?
---
htdocs/gcc-12/changes.html | 25 -
1 file changed, 24 insertions(+), 1 deletion(-)
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 4f2ee77f..c924bca3 100644
--- a/htdocs/gcc
On 4/5/22 17:14, Thomas Schwinge wrote:
Hi!
Still catching up with GCC/nvptx back end changes... %-)
In the following I'm not discussing the patch to document
"gcc-12: Nvptx updates", but rather one aspect of the
"gcc-12: Nvptx updates" themselves. ;-)
On 2022-03-30T14:27:41+0200, Tom de Vr
16:14
> To: Tom de Vries ; Jakub Jelinek
> Cc: gcc-patches@gcc.gnu.org; Tobias Burnus ;
> Roger Sayle
> Subject: Proposal to remove '--with-cuda-driver' (was: [wwwdocs][patch] gcc-
> 12: Nvptx updates)
>
> Hi!
>
> Still catching up with GCC/nvptx b
Am Tue, 5 Apr 2022 08:30:32 +0200
schrieb "Richard Biener" :
> If you have git write access you should add yourself in the DCO
> section in the MAINTAINERS file. Otherwise it has been said it's
> enough to explicitly state in mail that you are contributing this
> change under the Developer's Cert
Hi!
Still catching up with GCC/nvptx back end changes... %-)
In the following I'm not discussing the patch to document
"gcc-12: Nvptx updates", but rather one aspect of the
"gcc-12: Nvptx updates" themselves. ;-)
On 2022-03-30T14:27:41+0200, Tom de Vries wrote:
> + The -march flag has been
On Tue, Apr 5, 2022 at 8:06 AM Arnaud Charlet via Gcc-patches
wrote:
>
> > Thank you for the feedback. Should I remove it and resuply the patch or
> > can you/GCC maintainers do the modification before merging?
>
> Can you please resubmit it?
>
> I'll let others comment on the need to sign a contr
> Thank you for the feedback. Should I remove it and resuply the patch or
> can you/GCC maintainers do the modification before merging?
Can you please resubmit it?
I'll let others comment on the need to sign a contributor agreement, my
understanding is that this is unavoidable, whether you're con
Am Mon, 04 Apr 2022 23:51:24 +0200
schrieb "Eric Botcazou" :
> Thanks for your contribution. Small nit:
>
> + Support for 128bit integers has beed added.
>
> The support was already present in GCC 11, the criterion being the
> use of the 'Max_Integer_Size attribute in system.ads.
>
> --
> Eric B
> this is my first patch to GCC, if there is anything off, please, say
> so. I have used the default HTML formatting that comes with Emacs. I
> have created the patch using the `git format-patch` utility.
Thanks for your contribution. Small nit:
+ Support for 128bit integers has beed added.
Th
Hi,
this is my first patch to GCC, if there is anything off, please, say
so. I have used the default HTML formatting that comes with Emacs. I
have created the patch using the `git format-patch` utility.
One thing that may not be allowed (I am not aware of any rule against
it but still) is the amo
On Tue, 15 Mar 2022, Jonathan Wakely wrote:
>> It appears redhat.com has lost Fedora mailing list archives, which are
>> now at lists.fedoraproject.org using completely different tooling.
>>
>>Jakub, is there a better way than the patch below?
> This looks right to me, I don't think there's a bette
I - or rather the w3 validator :) - realized that the use of
is deprecated, so use id attributes instead.
Gerald
---
htdocs/gcc-11/changes.html | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index 8e6d4ec8..c9eb22
Document PR102024 change (r12-7961 and 7962) for MIPS. Ok for wwwdocs?
--
htdocs/gcc-12/changes.html | 17 -
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 4e1f6b0f..a2d8156f 100644
--- a/htdocs/gcc-12
I've committed the following patch to the GCC 12 release notes.
---
htdocs/gcc-12/changes.html | 47 --
1 file changed, 30 insertions(+), 17 deletions(-)
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index f1c36258..5619acff 100644
--- a
I've gone ahead and committed the following change to the GCC 12
release notes.
---
htdocs/gcc-12/changes.html | 35 ++-
1 file changed, 34 insertions(+), 1 deletion(-)
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 689feeba..f1c36258 1
[ was: Re: [wwwdocs][patch] gcc-12/changes.html: Document -misa update
for nvptx ]
On 3/3/22 13:27, Tobias Burnus wrote:
The current wording, https://gcc.gnu.org/gcc-12/changes.html#nvptx ,
is outdated and (now wrongly) encourages to use -mptx=.
Updated as follows.
I've taken these ch
M and AArch64 backends refer to this in their -Wpsabi
diagnostics.
Ok for wwwdocs?
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 689feeba..dc0e4074 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -28,6 +28,31 @@ a work-in-progress.
Ca
Doesn't this need the anchor that the compiler links to?
#zero_width_bitfields
R.
On 30/03/2022 11:07, Jakub Jelinek via Gcc-patches wrote:
Hi!
This patch documents the PR102024 ABI changes.
The x86-64, ARM and AArch64 backends refer to this in their -Wpsabi
diagnostics.
Ok for ww
On Wed, Mar 30, 2022 at 01:00:43PM +0200, Richard Biener wrote:
> > --- a/htdocs/gcc-12/changes.html
> > +++ b/htdocs/gcc-12/changes.html
> > @@ -28,6 +28,31 @@ a work-in-progress.
> >
> > Caveats
> >
> > +
> > +An ABI incompatibility between C and
> > +C++ when passing or returning
On Wed, Mar 30, 2022 at 12:08 PM Jakub Jelinek via Gcc-patches
wrote:
>
> Hi!
>
> This patch documents the PR102024 ABI changes.
> The x86-64, ARM and AArch64 backends refer to this in their -Wpsabi
> diagnostics.
> Ok for wwwdocs?
>
> diff --git a/htdocs/gcc-12/c
Hi!
This patch documents the PR102024 ABI changes.
The x86-64, ARM and AArch64 backends refer to this in their -Wpsabi
diagnostics.
Ok for wwwdocs?
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 689feeba..dc0e4074 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs
In case it's helpful, I've included copies of the patches as
attachments (as well as a single patch that is all of these changes
merged together).
--Poke
On Tue, Mar 22, 2022 at 12:50 PM Pokechu22 wrote:
>
> While working on a separate patch, I found several typos on the website.
> I have only l
Committed.
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 9cff81b9..689feeba 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -193,6 +193,27 @@ a work-in-progress.
+C
+
+ Some new features from the upcoming C2X revision of the ISO C
+
Pushed to wwwdocs.
---
htdocs/gcc-12/porting_to.html | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/htdocs/gcc-12/porting_to.html b/htdocs/gcc-12/porting_to.html
index 470703c7..079bda30 100644
--- a/htdocs/gcc-12/porting_to.html
+++ b/htdocs/gcc-12/porting_to.html
---
htdocs/contribute.html | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/htdocs/contribute.html b/htdocs/contribute.html
index c0223738..2d04b1f0 100644
--- a/htdocs/contribute.html
+++ b/htdocs/contribute.html
@@ -267,7 +267,7 @@ characters.
The classifier identifi
---
htdocs/codingrationale.html | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/htdocs/codingrationale.html b/htdocs/codingrationale.html
index 0b44f1da..f523f3e2 100644
--- a/htdocs/codingrationale.html
+++ b/htdocs/codingrationale.html
@@ -18,7 +18,7 @@
Inlining funct
---
htdocs/codingconventions.html | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/htdocs/codingconventions.html b/htdocs/codingconventions.html
index e4d30510..86b63b89 100644
--- a/htdocs/codingconventions.html
+++ b/htdocs/codingconventions.html
@@ -141,7 +141,7 @@ a la
---
htdocs/branch-closing.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/branch-closing.html b/htdocs/branch-closing.html
index c36ad1ab..15fb90e3 100644
--- a/htdocs/branch-closing.html
+++ b/htdocs/branch-closing.html
@@ -54,7 +54,7 @@ is listed in "Known to work
While working on a separate patch, I found several typos on the website.
I have only looked within the htdocs directory, not its subdirectories.
These are individual patches per file, since that seemed reasonable to me.
I believe this is a small enough change that I do not need to go through
copy
It was high time I updated our C++ DR table.
Pushed.
---
htdocs/projects/cxx-dr-status.html | 153 +++--
1 file changed, 122 insertions(+), 31 deletions(-)
diff --git a/htdocs/projects/cxx-dr-status.html
b/htdocs/projects/cxx-dr-status.html
index b49a97f2..63ec6d51 1006
On 12/03/22 22:55 +0100, Gerald Pfeifer wrote:
I have *NOT* pushed this yet, looking for feedback:
It appears redhat.com has lost Fedora mailing list archives, which are
now at lists.fedoraproject.org using completely different tooling.
Jakub, is there a better way than the patch below?
This
701 - 800 of 1779 matches
Mail list logo
