On Thu, Apr 17, 2025 at 5:31 PM Jerry D wrote:
>
> I now see this in git:
>
> remotes/origin/releases/gcc-15
>
> So we are at or very close to the release.
Very close. See https://gcc.gnu.org/pipermail/gcc/2025-April/245943.html .
Thanks,
Andrew
>
> Cheers,
>
> Jerry
On Tue, Jan 28, 2025 at 10:32 AM Jerry D wrote:
>
>
> Before I go clicking on links, is this legit? I presume patches are
> getting checked before being pushed.
Yes this is a legit email from the Linaro automation.
And yes patches are being tested before they get pushed to help
developers just in
(gfc_trans_transfer): Add default case.
Signed-off-by: Andrew Pinski
---
gcc/fortran/trans-io.cc | 2 ++
1 file changed, 2 insertions(+)
diff --git a/gcc/fortran/trans-io.cc b/gcc/fortran/trans-io.cc
index 906dd7c6eb6..9b0b8cfdff9 100644
--- a/gcc/fortran/trans-io.cc
+++ b/gcc/fortran/trans
stdinc:-fintrinsic-modules-path finclude%s}" \
TARGET_F951_OPTIONS \
"%{!fsyntax-only:%(invoke_as)}"
...
{"@f95",
"f951 %i %{E:%{!cpp:%egfortran does not support -E without -cpp}}\
%{cpp:" F951_
gned"
+ }
set nshort [file tail [file dirname $test]]/[file tail $test]
list-module-names $test
```
should work but I am not 100% I got the TCL syntax correct.
Thanks,
Andrew Pinski
>
> Best regards
>
> Thomas
cification (or the compiler
> silently ignored them because they were not applicable to my machine -
> ugh), the cause of the problem lies elsewhere.
AARCH64 armv8-a has FMA as part of its base ISA.
So you want to try with `-ffp-contract=off` instead.
RDMA turns on/off instructions which
4 includes an FMA instruction but since the base ISA
does not include it, it is not enabled by default.
I am suspect the aarch64 "excessive exceeding the threshold for
errors" are all caused by the more use of FMA rather than anything
else.
Thanks,
Andrew Pinski
>
> diff lapack-amd
On Tue, Apr 9, 2024, 10:07 H.J. Lu wrote:
> Since Glibc 2.34 all pthreads symbols are defined directly in libc not
> libpthread, and since Glibc 2.32 we have used __libc_single_threaded to
> avoid unnecessary locking in single-threaded programs. This means there
> is no reason to avoid linking to
On Sun, Mar 24, 2024 at 1:19 PM Harald Anlauf wrote:
>
> Dear all,
>
> I noticed by chance that we have quite a lot of improperly specified do-do
> directives in the testsuite.
>
> % grep "dg-do run" gcc/testsuite/gfortran.dg/ -rl|wc -l
> 83
>
> Note that with two blanks instead of just one a tes
On Wed, Sep 27, 2023 at 11:28 PM Richard Biener via Fortran
wrote:
>
> On Wed, Sep 27, 2023 at 11:48 PM Jeff Law via Fortran
> wrote:
> >
> >
> >
> > On 9/27/23 12:21, Toon Moene wrote:
> >
> > >
> > > The lto-ing of libgfortran did succeed, because I did get a new warning:
> > >
> > > gfortran -
On Tue, Sep 26, 2023 at 11:39 PM Richard Biener via Fortran
wrote:
>
> On Tue, Sep 26, 2023 at 4:44 PM Lingadahally, Vishakha (2023)
> wrote:
> >
> > Dear GCC Team,
> >
> > I'm running Ubuntu 22 on my Mac virtually and my gfortran version is
> > 11.4.0. When I try to install a certain software p
So the problem here is EXPAND_INTER_MACRO_16 expands to nothing if 16 byte FP
does not
exist but we still add a comma after it and that causes a build failure.
The same is true for EXPAND_INTER_MACRO_10 too.
Committed as obvious after a bootstrap and test on x86_64-linux-gnu and
aarch64-linux-gn
ng to rebuild
> them. If there aren't any equivalent libraries then I may need to work on
> getting the Intel compiler added to the software list, which will take
> another month or more.
Please read https://gcc.gnu.org/legacy-ml/fortran/2010-04/msg00314.html
for about DFPORT and
On Tue, Nov 15, 2022 at 7:47 AM Martin Liška wrote:
>
> Hi.
>
> I've just pushed libsanitizer update that was tested on x86_64-linux and
> ppc64le-linux systems.
> Moreover, I run bootstrap on x86_64-linux and checked ABI difference with
> abidiff.
This broke hwasan on aarch64. See https://gcc.
On Fri, Apr 28, 2023 at 8:32 AM Jerry D via Fortran wrote:
>
> Hello all and gcc overseers,
>
> I received a notice that the MasterMost server providers decided to drop
> their free service. Unfortunate and understandable.
>
> I plan to contact the Open Software Lab folks at Oregon State Universit
The problem here is we were outputing long_long instead of
"long long". This was just an oversight and a missing check.
Committed as obvious after a bootstrap/test on x86_64-linux-gnu.
gcc/fortran/ChangeLog:
* dump-parse-tree.cc (get_c_type_name): Fix "long_long"
type name to be
On Wed, Mar 1, 2023 at 3:52 PM Bernhard Reutner-Fischer
wrote:
>
> On Wed, 1 Mar 2023 14:59:44 -0800
> Andrew Pinski wrote:
>
> > On Wed, Mar 1, 2023 at 1:31 PM Bernhard Reutner-Fischer via Fortran
> > wrote:
> > >
> > > Hi!
> > >
|2 +-
> zlib/examples/gzjoin.c |3 +--
> zlib/examples/gzlog.c|6 ++
zlib is definitely imported from zlib upstream.
So it might be good to check if we could import a new version and see
if it still works instead.
Thanks,
Andrew Pinski
>
> cocc
dardizing a new POSIX makefile syntax rather
than changing C++ here.
Thanks,
Andrew Pinski
>
> [P1689R5]: https://isocpp.org/files/papers/P1689R5.html
>
> I've also added patches to include imported module CMI files and the
> module mapper file as dependencies of the compilation
t a failure if there was a duplicated one and then dg-message to
match the original message just to make sure it is outputted once
(dg-message was because it was originally a note: rather than a
warning/error but similar thing can be done for dg-error/dg-warning).
Thanks,
Andrew Pinski
>
> Thanks,
> Harald
>
; + else if (TREE_CODE (bound) == INTEGER_CST
> + && wi::to_wide (bound) == type_max
> + && TYPE_PRECISION (type) != 1)
> +return xstrdup ("+INF");
> + else
> + return print_generic_expr_to_str (bound);
No reason to do xstrdup any more either.
>
HOST_BITS_PER_PTR (CHAR_BIT * SIZEOF_VOID_P)
Where SIZEOF_* are defined while doing a configure and CHAR_BIT is
defined in limits.h which is defined as a preprocessor constant.
Does that help you understand the code better?
Thanks,
Andrew Pinski
>
> Thanks for any enlightenment,
> Harald
>
22 matches
Mail list logo
