rather than
always using some fallback implementation that ends up calling the
"normal" trig functions. Not sure how that should be implemented,
maybe some kind of weak symbol trickery to use the libgfortran
fallback implementations in case libm doesn't provide it?
--
Janne Blomqvist
between "benign" extensions and dangerous ones, though there might be
improvements to be made of how the bitflags are handled and passed to
the runtime.
I can sympathize with the desire to make the standard behavior the
default, but the reality is probably that you'll drown in bug rep
e template for every type and export the symbol
void matmul_r4(gfc_array_r4* a, gfc_array_r4* b, gfc_array_r4* c, ...)
{
matmul(a, b, c, ...);
}
// And so on for other types
}
--
Janne Blomqvist
e target libm includes
those or not they are then included in the exported symbol list.
It's possible to override this to look for specific symbol versions
etc., but that probably goes deep into the weeds of target-specific
stuff (e.g. are we looking for cospi@FBSD_1.7, cospi@GLIBC_X.Y.Z, or
something else?). I'm sure you don't wanna go there.
--
Janne Blomqvist
on. We could generate that code directly in the front-end, couldn’t
> we?
The frontend generally doesn't know what the target libm implements,
hence it's better to just generate the call, and if necessary have a
barebones implementation in libgfortran if libm doesn't implement it
properly.
--
Janne Blomqvist
pet added then which is still there.
Per analysis done then, it seems SunOS 4 was the last system where
free() of a NULL pointer didn't behave per the spec.
Also in Jim's patch intl/ and zlib/ directories were not touched as
those are imported from other upstreams.
--
Janne Blomqvist
king on the compiler outright, could be a
way of growing the open source Fortran programmer base, which could
eventually grow into contributors to the compiler itself? In
particular if they want to use some newfangled Fortran feature that
doesn't work in GFortran; scratching your own itch is always a good
motivator!
--
Janne Blomqvist
8 mentions changing int to bool, where
appropriate, which I think is uncontroversial, but this?
--
Janne Blomqvist
I'm not personally working on
GFortran at this time so somebody else would have to pick it up.
--
Janne Blomqvist
for pointing out that -g does not make the code slower.
> > Is there an option that prevents the sourcecode to be included when -g is
> > used?
You might try -frecord-gcc-switches. There's also
-grecord-gcc-switches (which puts the info somewhere in the debug
data), which is enabled b
On Thu, Jun 2, 2022 at 10:33 PM Kay Diederichs
wrote:
> Am 02.06.22 um 21:06 schrieb Janne Blomqvist:
> > As an alternative approach, make a command-line option (say, "-v")
> > that prints the version number of the program, name of the author and
> > other pertin
e program, name of the author and
other pertinent information, as well as the output of
compiler_version() and compiler_options(), and then exits. That would
ensure that those calls won't be optimized away.
--
Janne Blomqvist
12 matches
Mail list logo
