On 9/25/24 3:18 AM, Andre Vehreschild wrote:
Hi all,
I finally managed to apply the fixed patch. It still had some stray line break
so check_GNU_style.py wouldn't succeed. But with that fixed I agree to have
only some nonsense bickering of the script.
As to the patch (I have stripped large part
Am 07.01.25 um 17:52 schrieb Jakub Jelinek via Gcc:
But the compiler does in every ICE message in which -freport-bug isn't
enabled.
It seems that -freport-bug does nothing for Fortran, or at least the
Fortran front end (which why it was unfamiliar to me). Grabbing a
random ICE off bugzilla, sli
Hi Steve,
On Tue, Jan 07, 2025 at 03:28:31PM +0100, Thomas Koenig wrote:
Hello world,
the attached patch does what it says in the ChangeLog entry.
Tested with "make dvi" and "make pdf".
OK for trunk?
OK.
Committed. Thanks!
Best regards
Thomas
On Tue, Jan 07, 2025 at 03:28:31PM +0100, Thomas Koenig wrote:
> Hello world,
>
> the attached patch does what it says in the ChangeLog entry.
>
> Tested with "make dvi" and "make pdf".
>
> OK for trunk?
>
OK.
--
Steve
Hello world,
the attached patch does what it says in the ChangeLog entry.
Tested with "make dvi" and "make pdf".
OK for trunk?
Best regards
Thomas
Document unsigned constants in intrinsic modules.
gcc/fortran/ChangeLog:
* intrinsic.texi (ISO_FORTRAN_ENV): Also
Hi Jerry,
thanks again for the review. Pushed as gcc-15-6618-g25b380dc63c.
Regards,
Andre
On Mon, 6 Jan 2025 09:15:39 -0800
Jerry D wrote:
> On 1/6/25 2:08 AM, Andre Vehreschild wrote:
> > Hi all,
> >
> > attached patch has been rebased to latest trunk. Just pinging!
> >
> > Regtests o
Hi Jerry,
thanks for the review. Pushed as gcc-15-6615-gd8970909490
with the tweak ;-)
Have a good year and thanks again,
Andre
On Mon, 6 Jan 2025 09:13:27 -0800
Jerry D wrote:
> On 1/6/25 6:21 AM, Andre Vehreschild wrote:
> > Hi all,
> >
> > during looking for something completely di
