Hello,
I have a novice question to dg-error. The testcase if for Fortran, but I
hope to find more dejagnu experts here
I have:
> gcc/testsuite/gfortran.dg> cat -n namelist_internal2.f90 | grep dg-
1 ! { dg-do compile }
2 ! { dg-options "-fall-intrinsics -std=f95" }
16write(st
Hi,
if I dump the tree of the following C program,
int main() { volatile int i; i = 5; return 0; }
I get (-tree-original):
{
volatile int i;
volatile int i;
i = 5;
return 0;
}
However, if I apply my volatile-in-Fortran patch [1] and compile
integer, volatile :: i; i = 5; end
then t
Hi,
gfortran provides via ISO C Bindings access to the C types int, float
etc. It also provides access to int_fast8_t, int_fast16_t, etc. of stdint.h.
Using "#include " with e.g. sizeof(int_fast8_t) does not work
with cross compilations. (It actually fails already for -m32 on x86-64.)
On the othe
Ross Ridge wrote:
> Danny Smith writes:
>> Unless you are planning to use a gfortran dll in a VisualBasic app, I
>> can see little reason to change from the default "C" calling convention
>
> FX Coudert writes:
>> That precise reason is, as far as I understand, important for some
>> people. Fortran
Hi Yusuke, hi all,
On 3/2/20 12:16 PM, Thomas Koenig wrote:
Would you tell me more information about the project?
Before the introduction of modules and "contained" procedures
(both: Fortran 90), there was no way to declare/define a function
at one place and when using the procedure to know (a
CC overseers.
they are not stripped – I do see them both in my inbox and at
https://gcc.gnu.org/pipermail/fortran/2020-March/054050.html
However, attachments of the "text/x-…" format (here: text/x-patch)
are no longer shown inline but have to be downloaded (with the
inconvenient suffix: .bin) –
Hi Thomas, hi Overseers
I can confirm that those are stripped off!
I did sent an email with three attachments:
* test.txt (text/plain)
* test.diff (text/x-diff)
* the company's disclaimer
The attachment with 'text/x-diff' MIME was removed :-(
See: https://gcc.gnu.org/pipermail/fortran/current/0
That's a known to-do item – see "cvsweb/svn" under
https://sourceware.org/sourceware-wiki/MigrationWorkItems/?updated
Tobias
On 3/18/20 9:07 PM, Nicholas Krause via Gcc wrote:
On 3/18/20 3:49 PM, Martin Sebor via Gcc wrote:
I've been getting Error 403 (Forbidden - You don't have permission
t
-fsanitize=address should work – but I think you
need to create gfortran.dg/asan/asan.exp, e.g. by
copying gcc.dg/asan/asan.exp and adapting it.
That not only checks for double free but also for
instruments the code for use-after-free errors.
Cheers,
Tobias
On 4/29/20 9:23 PM, Thomas Koenig vi
On 5/4/20 9:05 PM, Jakub Jelinek via Gcc wrote:
On Mon, May 04, 2020 at 08:56:16PM +0200, Martin Liška wrote:
What's missing right now is how will we declare a Backport format.
Can we just use something like: 'Backport from
6607bdd4c834f92fce924abdaea3405f62dc'?
No. What we should allow i
On 6/5/20 4:11 PM, Jakub Jelinek via Gcc wrote:
It is glibc that provides them, not GCC.
See
https://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/x86/fpu/bits/math-vector.h;h=0801905da7b85e2f43fb6b682a7b84c5eec469d4;hb=HEAD
Minor addition: That header file is included in math.h, i.e. autom
er: Thomas Heurung, Alexander
Walter
commit b7dd405948d12e005ce4ebe665120fa028e050b4
Author: Tobias Burnus
Date: Mon Aug 3 09:35:49 2020 +0200
Fortran texi: Fix typos
gcc/fortran/ChangeLog
* gfc-internals.texi: Fix typos.
* gfortran.texi
On 8/26/20 5:17 PM, Joseph Myers wrote:
The SC has approved Tobias Burnus as an additional OpenACC maintainer.
Tobias, please add yourself as OpenACC maintainer to the MAINTAINERS file.
Thanks to the SC for the trust; I also have now updated that file.
Tobias
-
Mentor
On 9/25/20 8:02 AM, Thomas Koenig via Fortran wrote:
for review of its patches, gfortran relies on a group of people
who can approve patches. Unfortuntately, many of them are not
active. Others, who have the capability and who have acted as
de facto approvers (without anybody minding) are missi
On 19.11.20 12:03, Thomas Schwinge wrote:
As far as I can tell, we (GCC) don't currently state the minimum CUDA
version supported: for nvptx target, and especially then for
OpenACC/OpenMP nvptx offloading.
The nvptx target generates ".version 3.1" (= PTX ISA version) code
with ".target sm_30"
Hi Thomas,
On 06.12.20 10:22, Thomas Koenig via Gcc wrote:
it seems that git commits are no longer automatically transferred
to the relevant PRs.
In principle, that still works. See "cvs-commit" at
https://gcc.gnu.org/pipermail/gcc-bugs/2020-December/date.html#end
Recently, there were issues
Hi Thomas,
On 07.12.20 09:27, Tobias Burnus wrote:
However, what puzzles me is
https://gcc.gnu.org/pipermail/gcc-cvs/2020-December/338684.html – this
is your commit. But while in the commit, I see "Koenig" for both
'Author' and 'Commit', the 'From:' of
Hi Thomas,
On 08.12.20 19:34, Thomas Koenig via Fortran wrote:
I would like to know the name of a variable created with
create_tmp_var_raw, but it is not clear to my how to do it.
...
t = create_tmp_var_raw (type, prefix);
-
+ dprintf (2, "%s\n", IDENTIFIER_POINTER (DECL_NAME (t)));
I thin
Hi Thomas,
which binutil version do you have? I am asking because Jakub just
submitted:
https://gcc.gnu.org/pipermail/gcc-patches/2021-January/564206.html
If that does not help, it might be that valgrind simply does not like
the DWARF which GCC now produces by default.
Defaulting to 4: Well, on
first argument.
"
Should be "minimum value"
Best,
Russ Childers
-
Mentor Graphics (Deutschland) GmbH, Arnulfstrasse 201, 80634 München
Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Frank
Thürauf
commit 9dcc2edfa657d26223f7e74d27af225d4bb
Hi Krishna,
On 03.04.21 13:52, Krishna Kariya wrote:
I am Krishna, a final-year undergraduate student from India. I am
interested in the project “Fortran – run-time argument checking” for
GSoC 2021. Please share some resources about the project. Please point
to some issues or programming tasks t
I think gfortran's result *is* *correct* according to the
Fortran standard.
(I concur that the result is not what one would expect but
it is now decades to late to change that.)
sudo.michio wrote:
> I have an trouble in E edit descriptor of gfortran.
> This is a example.
...
> write(*,'(e
Roman Gareev wrote:
I've created an account on the gcc wiki but I don't allowed to create
and edit any page. I would like to set up a wiki page to post the
updates of the project after reaching my mile stones. Could you please
advise me how to get appropriate rights?
I have added you to the edi
Tejas Belagod wrote:
Are there any tricks I can use to debug an LTO ICE?
See LTO section on https://gcc.gnu.org/wiki/A_guide_to_testcase_reduction
Tobias
This email is probably a bit premature as the OpenMPv4.0 and OpenACC
2.0a specs do not seem to handle Fortran 2003's polymorphic variables.
However, as I am currently thinking how to handle a similar problem for
Fortran's coarray, I want to raise the issue for OpenMP/OpenACC to see
whether some
Hello all,
I am trying to use BUILT_IN_ATOMIC_..., but it does not quite work. I am
calling them as:
tmp = builtin_decl_explicit (BUILT_IN_ATOMIC_LOAD_4);
tmp = build_call_expr_loc (input_location, tmp, 2, atom.expr, ...
That gives the following dump:
__atomic_store_n (&i, 5, 0);
__a
David Malcolm wrote:
I didn't see a place to post slides for Cauldron talks, so am posting
links to them here.
I have added the links to
https://gcc.gnu.org/wiki/cauldron2014#Slides_and_Notes
Does anyone know if any Cauldron talks were recorded?
At least the ones in Lecture Theatre One were
Good morning Jerome,
Jerome Huck wrote:
> I have warning with COMMON. The COMMONS are the same along the code...
> When compiled I have warnings with different sizes !!!
Well, neither /NO1/ nor /NO4/ are not the same size throughout the code.
> There were some bugs/issues in the past see :
Thos
Hi Joost,
VandeVondele Joost wrote:
> I've noticed that
> make -j -k check-fortran
> results in a serialized checking, while
> make -j32 -k check-fortran
> goes parallel.
I have to admit that I don't know why that's the case. However, I can answer
the next question, is presumably related to thi
On 11.09.2014 20:33, VandeVondele Joost wrote:
>For PR56408 we need some fix.
BTW, is there anything special about Fortran ? There are at least 180 test
files that contain 'dg-additional-sources' some in a very non-local way:
Well, the question is what you want to do with the different files.
On 12.09.2014 18:10, Manuel López-Ibáñez wrote:
Hi Maxim, Many thanks for your leadership and hard work administering this.
Also thanks from my side.
I would be interested in reading about the results of the projects and
evaluations. Please student (and mentors), could you provide some
detail
On 19.09.2014 11:03, Thomas Schwinge wrote:
Regarding linking the object file produced by Fortran openacc.f90 into
libgomp: (with the version that Jim already has internally checked in)
I find that libgomp then has undefined references to
_gfortran_internal_unpack and _gfortran_internal_pack.
On 22.09.2014 17:17, Thomas Schwinge wrote:
That works. For avoidance of doubt: just tag to the actual
implementation (which is enough to avoid the references to
_gfortran_internal_unpack and _gfortran_internal_pack), or also the
interfaces, as detailed in the following "pseudo patch":
Well, t
On 22.09.2014 17:31, Tobias Burnus wrote:
In case of OpenACC, the OpenACC semantics require that the argument is
contiguous. If users gets it wrong, it will be wrong either way: If
the variable is not packed and when it is packed (and the temporary
removed after the function call).
Post
Dominique Dhumieres wrote:
> The failures for the gfortran.dg/coarray_collectives_9.f90 are fixed
> with the following patch:
Looks good to me. The patch is OK with a ChangLog.
Thanks for the patch and sorry for the test fails.
Tobias
Hi all,
currently, contrib/download_prerequisites downloads isl-0.12.2 from
ftp://gcc.gnu.org/pub/gcc/infrastructure/$ISL.tar.bz2
However, that version has a bug which causes an ICE (PR 62289).
End of October, ISL 0.14 was released, which should contain a fix for
that issue. Hence, one should con
Richard Biener wrote:
On Thu, Nov 6, 2014 at 8:02 AM, Tobias Grosser wrote:
Also, as Tobias suggested we should raise the minimal supported isl level to
0.14 to be sure PR 62289 is fixed.
As I am testing with system isl/cloog that would be unfortunate as it means
I'd either drop testing graphi
Kirill Yukhin wrote:
> Support of OpenMP 4.0 offloading to future Xeon Phi was
> fully checked in to main trunk.
Thanks. If I understood it correctly:
* GCC 5 supports code generation for Xeon Phi (Knights Landing, KNL)
* KNL (the hardware) is not yet available [mid 2015?]
* liboffloadmic support
BACKGROUND
Currently, gfortran reads source files directly. If preprocessing is
enabled, it calls libcpp directly but writes the preprocessed output
into a temporary file, which is then read. In order to bring processing
closer to the common code, show macro expansion in error messages and
si
Mark Farnell wrote:
> Has OpenACC 2.0 support been merged into the trunk yet? If not, then
> is it contained in gomp-4_0-branch?
>
> If so, what parameters should I pass to ./configure to enable OpenACC
> 2.0, and relevant backends such as CUDA, MIC and other GPGPU/manycore
> architecture?
>
> Als
Mark Farnell wrote:
> So what parameters will I need to pass to ./configure if I want to
> support PTX offloading?
Pre-remark: I think that the https://gcc.gnu.org/wiki/Offloading page will be
updated, once the support has been merged to the trunk.
I think using the triplet "nvptx-unknown-none" i
Joel Sherrill wrote:
On 1/12/2015 10:30 AM, Andreas Schwab wrote:
Joel Sherrill writes:
FAIL: gfortran.dg/g77/f77-edit-x-out.f -Os output pattern test, is 1 2 3
1 2 3
, should match ^1 2 3(
|
|)1 2 3(
|
|)$
Where is the \r gone? The pattern has (\n|\r\n|\r).
I am not exactly sure wh
Joel Sherrill wrote:
run.txt is the cut and paste of the log file which reflects DejaGNU's
view of the run.
Which means that it hopefully matches every bit of the original output
and that no editor interferes by adding or removing line breaks.
Additionally, I think you are right that the "***
Hi Joel,
Am 12.01.2015 um 22:04 schrieb Joel Sherrill:
That was very close.
cat out.txt | \
perl -e '$in = join("", ); if ($in =~ m/^1 2 3(\n|\r\n|\r)1 2
3(\n|\r\n|\r)((\n|\r\n|\r)\*\*\* EXIT code 0)(\n|\r\n|\r)?$/s) { print
"matched\n" } else { print "not matched\n" };'
That won't work
On 26 January 2015 at 23:50, Fredrik Tolf wrote:
> Consider the following small program:
[...]
> When compiling this with a -march that supports the roundsd instruction, the
> floor() call seems to only be compiled to such an instruction if
> -funsafe-math-optimizations is specified.
>
> Why is th
Dear all,
GCC has been accepted as Google Summer of Code mentor organization,
https://www.google-melange.com/gsoc/homepage/google/gsoc2015
Time line:
* March 27: Deadline of Student applications (opens March 16)
* Until May 25: Community bonding
* May 25 to August 24: Coding time
Suggestions f
Dear all,
we have this year two good GSoC projects for which we managed to get a
slot and a mentor:
Erik Krisztián Varga will work on the "Addressing mode selection in
GCC". Citing the abstract: "CPU architectures often provide a variety of
ways to load and save data into memory and register
Cf. http://gcc.gnu.org/ml/gcc/2011-02/msg00109.html and
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47032
Seems as if one needs to add link-time tests to libgfortran for some of
the C99 functions - the compile checks exists and succeed.
Tobias
Original Message
Subject: AIX
Hello,
Fortran 2008 has a build in parallelization (Coarray [Fortran], CAF)
[1]. gfortran did the first steps to a communication-library version
[2]. The library will be based MPI.
There are two issues I like to discuss in this email:
a) configuring and building
b) Test-suite support
Let's
Dear all,
I have question how one can and should tell the middle end about
asynchonous/single-sided memory access; the goal is to produce fast but
race-free code. All the following is about Fortran 2003 (asynchronous)
and Fortran 2008 (coarrays), but the problem itself should occur with
all(?
On 04/15/2011 11:52 AM, Janne Blomqvist wrote:
Q1: Is __sync_synchronize() sufficient?
I don't think this is correct. __sync_synchronize() just issues a
hardware memory fence instruction.That is, it prevents loads and
stores from moving past the fence *on the processor that executes the
fence ins
Ian Lance Taylor wrote:
Does any gcc maintainer object to setting this up? It sounds like a
good idea to me.
I concur.
I think the simple way for you to do this is to just create an account
on the gcc bugzilla (http://gcc.gnu.org/bugzilla/). Then I can grant
that account the necessary right
On 05/30/2011 12:10 PM, Robert Beeporbop wrote:
I have some questions for the gcc developers:
Also, I had a couple other general development questions:
~ Has anyone been working on GPU support, automatically-utilized or
otherwise?
I have not used it - nor have I seen much documentation, bu
On 06/06/2011 11:47 AM, Richard Guenther wrote:
Looks like an accident, modifying both trunk and branches/fortran-dev.
But the git mirror splits it between the trunk and fortran-dev branches.
Jerry, can you fix it up please?
This has been fixed else thread (cf. "Strange commit from fortran-de
On 06/06/2011 02:00 PM, jerry DeLisle wrote:
This whole thing has me puzzled. The branch was created before go and
libgo existed on trunk. Then I did a plain vanilla merge and got a
whole bunch of tree conflicts just for those two directories. Then I
attempted to manually resolve those tree co
On 06/19/2011 06:04 PM, "C. Bergström" wrote:
3) Fortran HPC community as a whole - The majority of Fortran users I
know work in or around HPC. (I may be biased) With that I can't say
most of them care about open source at all. (Some do) They buy/use
PathScale/PGI/Intel and for the larger l
Mike Du wrote:
I am helping my 9th grader child to learn using Gfortran for computation
programming.
[...] But could not find any compiler to download. We are using Vista and
Window7.
There does not exist an official binary of the GCC. Having said that,
the MinGW project and the Cygwin proje
Dear all,
during the GCC Gathering I realized during the LTO debugging symbol
discussion that gfortran does not generate debug information for the OOP
features (cf. PR 49475).
The first issue to solve is which DWARF information one should generate.
I have only very limited knowledge of DWARF
Hi Janus,
On 06/28/2011 02:12 PM, Janus Weil wrote:
Btw, how was the London meeting? Anything interesting to report (Fortran-wise)?
General topics, cf. http://gcc.gnu.org/wiki/GCCGathering2011
Fortran wise:
- I met Paul and Thomas, we had some discussions - but the notes still
have to be comp
On 06/28/2011 04:21 PM, Michael Eager wrote:
DWARF has attributes for accessibility (e.g., public, private). If the
attributes are similar to those for C++, you should generate them in a
similar fashion.
Well, Fortran has public and private - but I am not sure in how far it
matches C++'s publi
Sho Nakatani wrote:
> Then I would like to ask you what I should do next.
>
> (A) Try to change implementation of libgomp following
> my current implementation.
>Then test and evaluate it using some applications.
>(I think Barcelona OpenMP Task Suite [3] contains good applications
>
Hello all,
I seek a tree attribute which tells that a "pointer" (in the
C/middle-end sense) does not alias with any other variable in the
translation unit (i.e. like "restrict"), but on the other hand, it
should prevent code movements and value assumptions across (impure)
function calls - as
On 07/13/2011 12:57 PM, Richard Guenther wrote:
On Wed, Jul 13, 2011 at 12:30 PM, Tobias Burnus wrote:
Example 2: Coarray with sync. The SYNC is not directly called, but via a
wrapper function to increase the fun factor.
subroutine sub(coarray)
integer :: coarray[*]
coarray = 5
On 07/13/2011 03:27 PM, Ian Lance Taylor wrote:
The C99 restrict qualifier doesn't mean that some random function can
change the memory to which the pointer points; it means that assignments
through pointer 1 can't change the memory to which pointer 2 points.
That is, restrict is all about whethe
On 07/13/2011 03:46 PM, Tobias Burnus wrote:
On 07/13/2011 03:27 PM, Ian Lance Taylor wrote:
[...]
it doesn't say anything about functions, and in general a call to a
function can change any memory pointed to by any pointer.
I misread the paragraph - in particular the last sentenc
On 07/14/2011 11:21 AM, Richard Guenther wrote:
That Fortran passes everything by reference is really really not helping
optimizers.
I think it also does not harm optimizers. The problem is just that
optimizers are not tuned for it - but for C with later (C99?) attached
qualifiers.
Whether
Hi,
Fortran 2008 has a do concurrent construct, where the programmer
guarantees that the result is independent of the order; e.g.
do concurrent (i = 1:10:2) ! from, to, step/stride
A(i) = sin(B(i))
end do
can be run as i = 1, 3, 5, 7, 9; in any permutation or in parallel.
The plan is
On 11/07/2011 07:32 PM, Francisco Llaryora wrote:
With the purpose of measuring the SpedUp by changing the number of threads.
I did run fourty times by changing the value OMP_NUM_THREAD from 1 to 40.
I run it in a node with 40 cores Xenon.4 Processors with 10 cores each one.
The next is time in
On 11/08/2011 09:10 AM, FX wrote:
> I've filed PR 51026
(http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51026). In the meantime,
how do I build "the old way", with just a C compiler? I tried to
configure with "--enable-languages=c,fortran --disable-build-with-cxx",
but the configure script still
Sewell, Granville wrote:
I know that gfortran 4.3 was not compatible with earlier versions (can't mix
object code), but now a
user is telling me that 4.6 is not compatible with 4.3, is that true?
The library .so version number of GCC 4.3 to 4.7 is the same and no
symbol was deleted from libgf
Hi Rainer,
Rainer Emrich wrote:
> error: 'I' undeclared (first use in this function)
That's PR 40863 and a patch has been posted to
http://gcc.gnu.org/ml/gcc-patches/2009-07/msg01520.html
That patch should also remove all those
> warning: no previous prototype for 'csinhf'
warnings.
Tobias
On 09/04/2009 05:04 PM, FX wrote:
> -- it's unarguably a glibc issue: if exp() is fast and expf() is
> slow, why doesn't glibc implement expf() by calling exp()? (yes, there
> can be other issues like rounding or so, but they can also be dealt
> with separately)
If I recall correctly, it is most
On 11/09/2009 12:03 AM, Basile STARYNKEVITCH wrote:
> is gcc-trunk -flto -O2 aimed for medium sized programs (something like
> bash), or for bigger ones (something like the linux kernel, the Xorg
> server, the Qt or GTK graphical toolkit libraries, or bootstrapping GCC
> itself.
My understanding i
On 01/20/2010 12:17 PM, Piotr Wyderski wrote:
> is there something like an unofficial documentation
> of trunk features
Well, for the new features in the trunk: Have a look at the release
notes for the upcoming version 4.5 at
http://gcc.gnu.org/gcc-4.5/changes.html
For C++ 0x (1x?) have also a loo
Hi,
> Is there a way to update my SSH authorized_keys on gcc.gnu.org? I
> tried
As written at http://sourceware.org/cgi-bin/pdw/ps_form.cgi
ssh sourceware.org updatekey < ~/.ssh/id_dsa.pub
should do the deed.
Tobias
Hello all,
I have a library-usage question to the SC, a (wrapping) library
building/shipping question to GCC@ readers, and, of course, I also want
to announce the project a bit wider and seek for comments.
* * *
Coarrays are an extension of Fortran, which date back to the 1990s but
have now be
Hi,
Tobias Grosser wrote:
> another patch. It contains:
>
> - Removal of documentation outside of common.opts for (-fgraphite,
> -floop-block, -floop-interchange, -floop-strip-mine)
> This means doc/invoke.texi.
> (Proposed by Richi)
While I agree that -fgraphite does not make sense as use
Robert Dewar wrote:
>> With regard to the top 10% performance, Absoft is simply comparing
>> the overall mean performance numbers from the Polyhedron Benchmark.
>> gfortran will never look good by that metric because there are at
>> least 2 programs that would benefit from in-lining non-contained
>
Emmanuel Fleury wrote:
>> Username : (**)
>> Password : (**)
>> Date of Birth :
>> Future Password : ()(Option)
>
> Do they really think that it will succeed ???
> I guess not.
I guess they do. For spam, the reply rate might be as low as low as 1 in
12 million, for pis
Hello,
I'm thinking about how to implement Fortran 2003's IEEE support in
gfortran. The IEEE allow
a) To set an IEEE value (NaN, INF, etc.)
b) Check whether a value is NaN, etc.
c) To query for IEEE capabilities (IEEE_SUPPORT_NAN, IEEE_SUPPORT_SQRT
(a sqrt() which has IEEE exception support), etc.
Joseph S. Myers wrote:
>> My biggest issue is that I don't see how I can compile-time evaluate the
>> following - or how to evaluate it at all:
>>
>> if (IEEE_SUPPORT_NAN(x)) &! should be always true (or false) on a
>> given system
>>
> See MODE_HAS_NANS etc. in real.h
>
Thanks. There I
Ben Elliston wrote:
>> I cannot find where to download gcc binary for Linux. Can you email me
>> the link? It's so confusing in the http://gcc.gnu.org/ web site.
>
> You should install gcc from your Linux distribution. It will be far
> easier.
To add: There are no binaries of GCC released by the
(Revision 143523)
+++ ChangeLog (Arbeitskopie)
@@ -1,3 +1,7 @@
+2009-01-20 Tobias Burnus
+
+ * invoke.texi (RANGE): RANGE also takes INTEGER arguments.
+
2009-01-19 Mikael Morin
PR fortran/38859
Index: intrinsic.texi
===
-
Hi Kaveh,
Kaveh R. GHAZI wrote:
> I'm trying to create complex number expressions that contain inf or
> nan in the imaginary part. I.e. (0 + inf I) or (0 + nan I).
If it does not need to be C (e.g. to try MPC in the middle end), you
could use Fortran:
! compile with gfortran -fno-range-check
co
Michael Meissner wrote:
> I am just starting to think about adding OpenCL support into future
> versions of GCC, as it looks like a useful way of programming highly
> parallel type systems, particularly with hetrogeneous processors. At
> this point, I am wondering what kind of interest people have
Toon Moene wrote:
>>> Can somebody with access to SPEC sources confirm / deny and file a bug
>>> report, if appropriate?
>>
>> It is an x87 bug only and has already been filed:
>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39856 and working on
>> being fixed already.
The reason that is was not f
Basile STARYNKEVITCH wrote:
> Shobaki, Ghassan wrote:
>> In some optimization passes it may be useful to know the programming
>> language that we are compiling. Is there a way to get that information
>> in the middle end and back end?
>
> I am not sure that would be a good idea. In fact you are su
Dear Gerald,
> /usr/test/gcc/gcc/fortran/intrinsic.c: In function 'add_sym':
> /usr/test/gcc/gcc/fortran/intrinsic.c:306: error: enum conversion in
> assignment is invalid in C++
Can you try whether the following patch works? If so, you can
commit it as obvious. (I cannot test/commit it until th
Dave,
Dave Korn wrote:
> I see there are two places in fortran/parse.c
Side remark: You know that the actual middle-end TREE is only generated
in trans*.c? Thus, all things which happen before like parse.c can be
still remodeled in trans*c.
> that call
> main_program_symbol(): either as a result
Dave Korn wrote:
>> Wouldn't the simplest thing be to rename the other main function - the
>> initialisation one that is automatically generated by create_main_function()?
>> It could be called anything different we liked, and it's not user-visible,
>> so
>> it ought to not be a problem to rena
Dave Korn wrote:
> Dave Korn wrote:
>> Dave Korn wrote:
>>> Tobias Burnus wrote:
>>>> I agree that for "main" the call to "__main()" should happend and thus
>>>> expand_main_function should be called. I'm not sure in about the exa
Jerry DeLisle wrote:
> I tested the above on x86-64 Linux. OK to commit.
Thanks for the review. Committed:
Sendinggcc/fortran/ChangeLog
Sendinggcc/fortran/trans-decl.c
Transmitting file data ..
Committed revision 148035.
Tobias
Dave Korn wrote:
>>> + main_identifier_node = get_identifier ("main");
>>> + ftn_main = build_decl (FUNCTION_DECL, main_identifier_node, tmp);
>>>ftn_main = build_decl (FUNCTION_DECL, get_identifier ("main"), tmp);
>>>
> I just took a second look at this. We surely didn't mean to buil
Hello,
Revital1 Eres wrote:
> I get the following error while bootstrap trunk -r148275 on ppc.
Worked with r148271 on x86-64-linux.
> -I../libdecnumber../../gcc/gcc/fortran/expr.c -o fortran/expr.o
> cc1: warnings being treated as errors
> ../../gcc/gcc/fortran/expr.c: In function גgfc_simp
On 05/06/2010 04:24 PM, Richard Guenther wrote:
> I would initially propose to make -Ofast be -O3 -ffast-math
> and would strongly encourage target maintainers that consider
> adding to -Ofast make sure that popular benchmarks for
> their target still behave correctly when using -Ofast.
I am in fa
Am 31.05.2010 20:50, schrieb Mark Mitchell:
> Gabriel Dos Reis wrote:
>
>> Yes, this is the sort of issues I have in mind. For example, I do not see
>> how
>> we can use C++ in tree.h without requiring other front-ends to use C++, at
>> least
>> for the parts that use tree.h. By components, I
Fixed in Rev. 160390 using the attached patch.
Thanks for the report!
Tobias
2010-06-07 Tobias Burnus
* gfc-internals.texi (copyrights-gfortran): Fix copyright year format.
* gfortran.texi (copyrights-gfortran): Ditto.
diff --git a/gcc/fortran/gfc-internals.texi b/gcc/fortran/gfc-intern
On 06/08/2010 05:42 PM, H.J. Lu wrote:
>> Think about mercurial or git. Every one can commit on his/her own
>> local repository, and "publish" his/her repository. [...]
>
> git is an excellent tool to create and share patches. Maybe we should
> have an open gcc git mirror with gitweb and every c
On 06/13/2010 03:09 PM, Gerald Pfeifer wrote:
> On Mon, 7 Jun 2010, Tobias Burnus wrote:
>
>>> It has been reported via the FSF that 'gfortran.info' is copyrighted by
>>> the FSF '1999-2008', although it should be under the form '1999, 2000,
On 06/22/2010 06:20 AM, Basile Starynkevitch wrote:
> Assuming a plugin (e.g. MELT) add a new pragma using PLUGIN_PRAGMAS, is
> this pragma usable from Ada or Fortran code?
>
> I am not very familiar with Ada or Fortran. I believe Ada has some
> syntax for pragmas -but do Ada pragma have the same
1 - 100 of 211 matches
Mail list logo
