On Wed, 2023-02-01 at 10:56 +0100, Gerald Pfeifer wrote:
> The original page is gone, and search engines did not reveal a new
> location.
>
> If any of you has a new location, feel free to add that (or let me
> know and I'll take care).
FWIW the most recent version in archive.org is here:
https:
On Thu, 2022-10-27 at 19:16 -0400, Ben Boeckel wrote:
> This simplifies the interface for other UTF-8 validity detections
> when a
> simple "yes" or "no" answer is sufficient.
>
> Signed-off-by: Ben Boeckel
> ---
> libcpp/ChangeLog | 6 ++
> libcpp/charset.cc | 18 ++
> lib
On Thu, 2022-10-27 at 19:16 -0400, Ben Boeckel wrote:
> Unicode does not support such values because they are unrepresentable
> in
> UTF-16.
Wikipedia pointed me to RFC 3629, which was when UTF-8 introduced this
restriction, whereas libcpp was implementing the higher upper limit
from the earlier,
On Mon, 2022-10-10 at 16:21 -0400, Jason Merrill wrote:
> On 10/4/22 11:11, Ben Boeckel wrote:
> > This patch adds initial support for ISO C++'s [P1689R5][], a format
> > for
> > describing C++ module requirements and provisions based on the
> > source
> > code. This is required because compiling C
Sorry in advance if this is a silly question; my knowledge of Fortran
is next to nothing, I'm afraid.
PR analyzer/107210 reports an ICE in -fanalyzer on this reproducer:
! { dg-additional-options "-O1" }
subroutine check_int (j)
INTEGER(4) :: i, ia(5), ib(5,4), ip, ipa(:)
target :: ib
POI
On Thu, 2022-01-06 at 17:20 +0100, Martin Jambor wrote:
> Hello,
>
> another year is upon us and Google has announced there will be again
> Google Summer of Code 2022 (though AFAIK there is no specific timeline
> yet). I'd like to volunteer to be the main Org Admin for GCC again so
> let me know
