-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/02/11 22:04, Tobias Burnus wrote:
Daniel Kraft wrote:
No regressions on x86_64-unknown-linux-gnu. Ok for trunk?
OK for the trunk and for 4.6 (as it is a regression).
And committed on 4.6 branch as rev. 177249, there also were
0UyNefZsrE0ziuWOAEvE
=hjnD
-END PGP SIGNATURE-
2011-08-02 Daniel Kraft d...@domob.eu
PR fortran/49885
* trans-array.c (gfc_trans_auto_array_allocation): Change
gfc_start_block to gfc_init_block to avoid spurious extra-scope.
2011-08-02 Daniel Kraft d...@domob.eu
PR
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/02/11 22:04, Tobias Burnus wrote:
Daniel Kraft wrote:
after a lng while, here's another patch from me. It is a
one-line fix for PR 49885, which was introduced by me last year.
While the patch should be simple, it wasn't that easy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Tobias,
On 06/06/11 23:40, Tobias Burnus wrote:
This patch adds incomplete parsing support for the LOCK and UNLOCK
statement. Missing part 2 is the addition of the LOCK_TYPE of the
ISO_FORTRAN_ENV.
Build and tested on x86-64-linux.
OK for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 05/31/11 18:24, Tobias Burnus wrote:
This patch adds the atomic_define and atomic_ref intrinsics. They are
currently implemented in form a simple assignment. For -fcoarray=lib
they will be replaced by a function call to
On 05/27/11 08:10, Tobias Burnus wrote:
Attached is a small coarray fix, solving two issues:
- For -fcoarray=single, nonallocatable coarrays are nonpointer - but
currently they get set the restrict qualifier. (With -fcoarray=lib,
nonallocatble coarrays are always pointers.)
Fixed by not
On 05/05/11 21:18, Tobias Burnus wrote:
Changes:
- Remove (not working) critical functions; a normal coarray of LOCK type
should be used instead. (Stub left in until it is removed the the front
end.)
- Added prototypes and stub implementations for
registering/deregistering coarray (currently
On 04/18/11 18:34, Tobias Burnus wrote:
Encountered them when testing IMAGE_INDEX.
Build and regtested on x86-64-linux.
OK for the trunk?
Ok.
Thanks!
Daniel
--
http://www.pro-vegan.info/
--
Done: Arc-Bar-Cav-Kni-Ran-Rog-Sam-Tou-Val-Wiz
To go: Hea-Mon-Pri
Hi,
On 04/07/11 21:32, Thomas Koenig wrote:
following Joost's request, the attached patch gives the user more
control over front end optimization - it can now be selected or
deselected independent of normal optimization. I have also implemented a
warning for eliminated functions.
Hi,
phil++ wrote:
I am a PhD student who has been working with CUDA for the GPU and also
gcc for Cell BE for about a year now. (By work I mean developing
applications). I am looking to bring GCC closer to being able to
support OpenCL as a Google Summer of Code. Here are some of my ideas:
1.
Toon Moene wrote:
All,
During the IRC meeting of GNU Fortran hackers last Friday, I was asked
to propose the following contributors to the Fortran compiler and run
time library for the position of reviewer to the Steering Committee:
Daniel Kraft
Janus Weil
Mikael Morin
Thanks Toon,
I
Arnaud Charlet wrote:
For half a year now, I've been working on the GCC Fortran front-end; but
I'm also quite interested in Ada as a language. However, I don't quite
like the idea that one needs a working Ada compiler to bootstrap the Ada
front-end. Well, it's the same with a C compiler to
12 matches
Mail list logo
