Thanks for your reply !
>The word "parameter" has very a specific meaning in Fortran. The
>entity that is passed into a function or subroutine is an "actual
>argument". The entity within the functions associated with the
>"actual argument" is a "dummy argument".
Can I understand "dummy parameters"
Hi Thomas,
Some updates here.
After some research, I realized that the nouveau driver may not be
sufficient for our workload, so the nvidia drivers are a must, along with
the CUDA toolchain. Fortunately, I got the drivers to work under Debian
when I disabled Secure Boot in the firmware. So we're
Hi, I'm sorry about the delay in sharing my proposal, submitting my
proposal for review.
https://docs.google.com/document/d/1Ffaqcm37d6W9IPAoYvg1jYShNjw-YNgaGVEeBW1B8oY/edit?usp=sharing
On Sat, Apr 05, 2025 at 03:16:45PM +0800, Gwen Fu wrote:
> My doubt :
> 1.Does the compilation option only need to support fortran versions above
> 9, o5r does it also need to support fortran 77?
gfortran started life as a Fortran 95 compiler. It should
support anything that is Fortran 95 or late
Snapshot gcc-15-20250406 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20250406/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 15 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Here is my initial draft for my proposal. Please provide as much feedback as
possible. Upon more research I realize I will almost definitely have time to do
more than just the bind and device_type clause. I have prepared significant
research for the cache directive as well, and could definitely
On 2025-04-06 10:46, Eldar Kusdavletov wrote:
Thanks, Andi — I’ve updated the proposal to reflect your feedback,
especially around separating frontend and backend phases. I now
describe the backend instrumentation as building on existing
per-function timevars and focusing on trace formatting and
