Status
==
The GCC development branch which will become GCC 13 is open for
general development (Stage 1). Stage 1 will end at the end of
November 13th after which we will accept no new features that
have not yet been submitted. Starting with Novemer 14th we
are in a two month general bugfixin
On 10/19/22 18:42, Joseph Myers wrote:
> On Wed, 19 Oct 2022, Martin Liška wrote:
>
>>> Currently, there is a tarball with texinfo sources for all the manuals
>>> for each version.
>>
>> Well, then equivalent would be packaging all .rst files together with the
>> corresponding
>> conf.py, logo.*
On 10/19/22 18:30, Sandra Loosemore wrote:
> On 10/19/22 05:09, Martin Liška wrote:
>> On 10/18/22 00:26, Sandra Loosemore wrote:
>>> On 10/17/22 07:28, Martin Liška wrote:
Hello.
Based on the very positive feedback I was given at the Cauldron Sphinx
Documentation BoF,
I'm
On 10/20/22 04:26, Xi Ruoyao wrote:
> On Mon, 2022-10-17 at 15:28 +0200, Martin Liška wrote:
>> Hello.
>>
>> Based on the very positive feedback I was given at the Cauldron Sphinx
>> Documentation BoF,
>> I'm planning migrating the documentation on 9th November. There are still
>> some minor comm
(CC our team members.)
On Thu, 2022-10-20 at 13:27 +0200, Martin Liška wrote:
> > Ouch. This will be very painful for Linux From Scratch. We'll need to
> > add 23 Python modules to build the documentation, while we only have 88
> > packages in total currently... And we don't want to omit GCC
>
On 10/20/22 13:49, Xi Ruoyao wrote:
> (CC our team members.)
>
> On Thu, 2022-10-20 at 13:27 +0200, Martin Liška wrote:
>>> Ouch. This will be very painful for Linux From Scratch. We'll need to
>>> add 23 Python modules to build the documentation, while we only have 88
>>> packages in total curr
On Thu, 2022-10-20 at 13:53 +0200, Martin Liška wrote:
> On 10/20/22 13:49, Xi Ruoyao wrote:
> > (CC our team members.)
> >
> > On Thu, 2022-10-20 at 13:27 +0200, Martin Liška wrote:
> > > > Ouch. This will be very painful for Linux From Scratch. We'll need to
> > > > add 23 Python modules to bu
On 10/20/22 13:55, Xi Ruoyao wrote:
> On Thu, 2022-10-20 at 13:53 +0200, Martin Liška wrote:
>> On 10/20/22 13:49, Xi Ruoyao wrote:
>>> (CC our team members.)
>>>
>>> On Thu, 2022-10-20 at 13:27 +0200, Martin Liška wrote:
> Ouch. This will be very painful for Linux From Scratch. We'll need to
On Thu, 20 Oct 2022, Martin Liška wrote:
> > Could generated man and info pages be provided as a tarball on
> > gcc.gnu.org or ftp.gnu.org?
>
> Not planning doing that.
Release tarballs (but not snapshots) currently include the info files and
man pages, via gcc_release running a build with
--e
On 10/18/22 08:18, Ben Boeckel wrote:
On Tue, Oct 11, 2022 at 07:42:43 -0400, Ben Boeckel wrote:
On Mon, Oct 10, 2022 at 17:04:09 -0400, Jason Merrill wrote:
Can we share utf8 parsing code with decode_utf8_char in pretty-print.cc?
I can look at factoring that out. I'll have to decode its logi
On 10/20/22 17:35, Joseph Myers wrote:
> On Thu, 20 Oct 2022, Martin Liška wrote:
>
>>> Could generated man and info pages be provided as a tarball on
>>> gcc.gnu.org or ftp.gnu.org?
>>
>> Not planning doing that.
>
> Release tarballs (but not snapshots) currently include the info files and
> ma
On Thu, 20 Oct 2022, Richard Biener via Gcc wrote:
> > 1. How should (...) be represented differently from unprototyped functions
> > so that stdarg_p and prototype_p handle it properly? Should I add a new
> > language-independent type flag (there are plenty spare) to use for this?
>
> I'd say u
On Thu, 20 Oct 2022, Martin Liška wrote:
> > Also, but not strictly part of the release issue:
> >
> > (d) Builds with missing or old Sphinx should work regardless of whether
> > such files are in the source directory - but if they aren't in the source
> > directory, the effect of missing or ol
On Thu, Oct 20, 2022 at 04:43:06PM +, Joseph Myers wrote:
> On Thu, 20 Oct 2022, Martin Liška wrote:
>
> > > Also, but not strictly part of the release issue:
> > >
> > > (d) Builds with missing or old Sphinx should work regardless of whether
> > > such files are in the source directory - bu
I'm working on adding various C2x features to the C front end (and
elsewhere in GCC as applicable).
I suspect I won't get all the C2x features done for GCC 13. If anyone
else is interested in adding C2x features, I'd encourage looking at some
of the following, which I may well not get to for G
On Thu, Oct 20, 2022 at 11:39:25 -0400, Jason Merrill wrote:
> Oops, I was thinking this was in gcc as well. In libcpp there's
> _cpp_valid_utf8 (which calls one_utf8_to_cppchar).
This routine has a lot more logic (including UCN decoding) and the
`one_utf8_to_cppchar` also supports out-of-bounds
On 10/20/22 13:31, Ben Boeckel wrote:
On Thu, Oct 20, 2022 at 11:39:25 -0400, Jason Merrill wrote:
Oops, I was thinking this was in gcc as well. In libcpp there's
_cpp_valid_utf8 (which calls one_utf8_to_cppchar).
This routine has a lot more logic (including UCN decoding) and the
`one_utf8_to
The FSF will host a public conversation and Q&A about the GTI project on:
October 24, 10am Eastern Time.
You can read the full details here:
https://www.fsf.org/events/the-gti-project-a-conversation-and-community-q-a
Everyone is welcome to submit questions, attend the event, and engage.
Thank y
Snapshot gcc-10-20221020 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/10-20221020/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 10 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
On Oct 18, 2022, Siddhesh Poyarekar wrote:
> The rest, AFAICT, are either fear of some kind of corporate takeover,
> discussions about current sourceware infrastructure, or just rhetoric,
> none of which I'm interested in engaging with.
So in which category do you place my question about the via
20 matches
Mail list logo
