Am 13.11.24 um 15:55 schrieb Toon Moene:
Since the Fortran 95 Standard it does (in the current Standard: 7.4.3.2
Real type):
The real type includes a zero value. Processors that distinguish between
positive and negative zeros shall treat them as mathematically equivalent
• in all intrinsic
Hello world,
J3, the US Fortran standards committee, has passed
https://j3-fortran.org/doc/year/24/24-179.txt
which states (with a bit of an overabundance of
clarity) that, in Fortran, it is possible special-case
complex multiplication when one of the numbers is known
to have a zero component, fo
[For the fortran people: Discussion on gcc@]
Just a general remark.
There are people, such as myself, who regularly mess up
their git repositories because they have no mental model
of what git is doing (case in point: The Fortran unsigned
branch, which I managed to put into an unrepairable state
Hello world,
when an ICE occurs somewhere when building a complex software package,
it can be cumbersome for the user to obtain the preprocessed file
that we ask people to submit to us.
Would it be reasonable to dump a preprocessed file (if any) on an ICE,
and point the user to it? The error me
Am 07.01.25 um 16:14 schrieb Jakub Jelinek via Gcc:
It is "debug information" in the sense that it is everything needed
to debug the ICE.
Which isn't just preprocessed source, but also used compiler options,
and details on how the compiler has been configured and what ICE has been
emitted. Plus,
Am 07.01.25 um 16:41 schrieb Thomas Koenig via Gcc:
Thanks for the explanation. I think it might be good to add a bit
of this to the docs. I will prepare a patch.
Side remark (which I will also address): https://gcc.gnu.org/bugs/ does
not mention -freport-bug.
Best regards
Thomas
Am 07.01.25 um 15:48 schrieb Jakub Jelinek:
On Tue, Jan 07, 2025 at 03:45:02PM +0100, Thomas Koenig via Gcc wrote:
Would it be reasonable to dump a preprocessed file (if any) on an ICE,
and point the user to it? The error message could then be something
like "Please submit the preproc
Am 07.01.25 um 18:04 schrieb Andreas Schwab:
On Jan 07 2025, Thomas Koenig via Gcc wrote:
Side remark (which I will also address): https://gcc.gnu.org/bugs/ does
not mention -freport-bug.
But the ICE message does.
Hm, OK.
Question: Would it make sense to enable -freport-bug by default on
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
Am 03.02.25 um 11:02 schrieb Mark Wielaard:
The problem is, as always spam... Do you find the current limit (400K)
restricts you often from fast posting to the gcc-patches list?
It happens every now and then, when the patches (as this one) are really
big.
(Does anybody actually look at the me
Am 10.02.25 um 21:05 schrieb David Malcolm:
FWIW my first thought for "interp" was that we gaining an interpreter
(there are some in the libgccjit test suite).
It was motivated by Fortran interps, which are interpretation requrests.
But I think that Richard's suggestion, neeeds-stdcheck, makes
Am 10.02.25 um 08:43 schrieb Richard Biener:
We have need-bisection and other need-, so iff then maybe a need-stdchk for
cases compliance is unclear?
That sounds very good to me; if there are no objections, I will create
this in a day or so.
The fact that a testcase is (non-)compliant is
also
Am 10.02.25 um 23:44 schrieb Thomas Schwinge:
Indeed 'need-language-lawyering' (or similar) would've been my suggestion
for the new keyword, but I resisted the color-of-bike-shed opportunity.
My fear would be that people would misspell laywer :-)
I've added needs-stdcheck and will go through a
Hi,
I sent https://gcc.gnu.org/pipermail/fortran/2025-February/061670.html
to gcc-patches also, as normal, but got back an e-mail that it
was too large. and that a moderator would look at it.
Maybe the limits can be increased a bit, sometimes patches can
be quite large, especially if they contai
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 not. I would propose to add a keyword for that, tentatively
called "interp".
Comments? Suggestions for a different name? Should I just go ahead
and
My commits have not been appearing in bugzilla for quite some time now.
Some recent examples have been
https://gcc.gnu.org/pipermail/gcc-cvs/2025-February/417177.html
https://gcc.gnu.org/pipermail/gcc-cvs/2025-February/417426.html
Is this a misconfiguration somewhere? Should I be doing something
Am 16.02.25 um 17:59 schrieb Thomas Koenig:
Am 16.02.25 um 16:29 schrieb Mark Wielaard:
For now I replaced Thomas last name with just "Koenig". Hope that
resolve the issue.
Thanks!
We'll see with the next commit.
... which worked, so the non-ASCII letters in the name seems t
Am 16.02.25 um 16:29 schrieb Mark Wielaard:
For now I replaced Thomas last name with just "Koenig". Hope that
resolve the issue.
Thanks!
We'll see with the next commit.
Best regards
Thomas
Hi Harald,
Hi Thomas,
On 5/11/25 10:34, Thomas Koenig via Gcc wrote:
As PR120139 has shown (again), it is too easy to create regressions
for dumping C prototypes from Fortran. The main problem
is that there is currently no test in the testsuite.
for something along this variant you can
As PR120139 has shown (again), it is too easy to create regressions
for dumping C prototypes from Fortran. The main problem
is that there is currently no test in the testsuite.
So, what to do? I see several possibilities:
1a) Change the relevant options so that they optionally
create a file (s
201 - 220 of 220 matches
Mail list logo
