On Wed, Jan 25, 2023 at 4:09 PM Ben Boeckel via Gcc wrote:
>
> This simplifies the interface for other UTF-8 validity detections when a
> simple "yes" or "no" answer is sufficient.
>
> libcpp/
>
> * charset.cc: Add `_cpp_valid_utf8_str` which determines whether
> a C string is vali
On Mon, 2023-10-23 at 11:24 -0400, Jason Merrill wrote:
> On 10/23/23 11:16, David Malcolm wrote:
> > On Wed, Jan 25, 2023 at 4:09 PM Ben Boeckel via Gcc
> > wrote:
> > >
> > > This simplifies the interface for other UTF-8 validity detections
> > > w
On Mon, 2024-01-15 at 18:48 +0100, Martin Jambor wrote:
> Hello,
>
> another year has passed, Google has announced there will be again
> Google
> Summer of Code (GsoC) in 2024 and the deadline for organizations to
> apply is already approaching (February 6th). I'd like to volunteer
> to
> be the
On Fri, 2024-10-11 at 15:34 +0100, Paul Richard Thomas wrote:
> Hi Tobias,
>
> Good catch! It looks 'obvious' to me too :-)
>
> Regards
>
> Paul
>
>
> On Fri, 11 Oct 2024 at 14:08, Tobias Burnus
> wrote:
>
> > I found always error.cc rather confusing but I just realized that
> > we can reduc
x whitespace. Pass
m_buffer to xhtml_builder::on_report_diagnostic.
(xhtml_output_format::xhtml_output_format): Initialize m_buffer.
(xhtml_output_format::m_buffer): New field.
* gfortran.dg/diagnostic-format-json-pr105916.F90: New test.
* gfortran
.
(gfc_pop_error): Likewise.
(gfc_diagnostics_init): Allocate error_buffer on the heap, rather
than statically.
(gfc_diagnostics_finish): Delete error_buffer.
Signed-off-by: David Malcolm
---
gcc/fortran/error.cc | 24 +---
1 file chang
On Wed, 2024-10-23 at 11:03 +0200, Tobias Burnus wrote:
> David Malcolm wrote:
> > In order to handle various awkward parsing issues, the Fortran
> > frontend
> > implements buffering of diagnostics, so that diagnostics reported
> > to
> > global_dc can be eithe
On Mon, 2025-02-10 at 09:29 +, Jonathan Wakely via Gcc wrote:
> On Sun, 9 Feb 2025, 09:08 Thomas Koenig via Gcc,
> wrote:
>
> > Hello world,
> >
> > looking at a few Fortran bug reports, I found some cases where
> > it was not clear if the program in question was standard-conforming
> > or n
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
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
ences are basically the changelog, some
> > style, and
> > `trtbd` instead of `p1689r5` as the format name).
> >
> > For testing within GCC, I'll work on the following:
> >
> > - scanning non-module source
> > - scanning module-importing source (`impor
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 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 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:
14 matches
Mail list logo
