Gerald Pfeifer wrote:
> We actually do have an issue with the Bugzilla instance on gcc.gnu.org
> being rather old, so if anyone with Bugzilla foo wants to donate time
> and effort, looking into upgrading that might be even preferrable.
See http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011 for more
(Off topic)
Basile Starynkevitch wrote:
> But you (whoever you really are) should also realize that to submit
> patches and have them accepted, you need to have some legal papers done
> with the FSF (copyright transfer or disclaimer, see the "legal
> prerequisites" section of http://gcc.gnu.org/co
Ralf W. Grosse-Kunstleve wrote:
Without knowing the compiler options, the results of any benchmark
are meaningless.
I used
gfortran -o dsyev_test_gfortran -O3 -ffast-math dsyev_test.f
If you work on a 32bit x86 system, you really should use -march=native
and possibly -mfpmath=sse - otherw
case -
as did delisting (after several hours).
Will do tomorrow. For now I have reverted this line of the patch
Le 28 août 2010 à 10:26, Tobias Burnus a écrit :
First question: Will you look at Andrew's patch - or should I do it? I fear we
are going to duplicate work.
OK. Thus,
Gerald Pfeifer wrote:
Do you have a pointer to testresults you'd like us to use for reference?
From our release criteria, for secondary platforms we have:
• The compiler bootstraps successfully, and the C++ runtime library
builds.
• The DejaGNU testsuite has been run, and a substant
Hello all,
given the optimization work which has gone into 4.6, I thought I would
run the Polyhedron Fortran test suite. The system is
- Intel Core2 Duo CPU E8400 @ 3.00GHz
- CentOS release 5.5 (Final) [x86-64]
Tested compilers:
- GCC 4.6 (recent nightly build)
- Intel Fortran compiler (if
Art Haas wrote:
My build this morning failed when libquadmath was being built. Things
failed when configuring in the 'amd64' subdirectory - the bits below
are taken from the 'config.log' in that directory:
There are two known problems:
a) libquadmath should - at least for now - only be build b
Why does everyone think that I and Fortran have something to do with it
if something breaks?* ;-)
The issue is known and a fix, which seemingly works on Darwin, exists.
See: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46510
Angelo Graziosi wrote:
/tmp/gcc-4.6-r166873/libgomp/barrier.c:41:1: int
Rainer Orth wrote:
While the build completed with the patch I've posted, fortran testing
for the non-default multilib is completely broken, e.g.
That's in a way the a duplicate of PR 46516. Or at least the solution is
similar: Getting rid of libgfortran.spec and fall back (again) to having
th
On 11/18/2010 07:50 AM, Ralf Wildenhues wrote:
* Rainer Orth wrote on Wed, Nov 17, 2010 at 09:15:55PM CET:
* One cannot -lm to libquadmath_la_LIBADD since that gets passed to nm,
which doesn't know (and doesn't need to be run) -lm.
That's a bug in the rule using nm then, though.
[...]
Using
Rainer Orth wrote:
Tobias Burnus writes:
Rainer Orth wrote:
While the build completed with the patch I've posted, fortran testing
for the non-default multilib is completely broken, e.g.
That's in a way the a duplicate of PR 46516. Or at least the solution is
I don't think so
On 11/19/2010 03:41 PM, Rainer Orth wrote:
Tobias Burnus writes:
No, finding libgfortran.spec at compile time works - it is all about
finding it at run time.
pardon me: AFAIK the spec files are *only* used by the compiler driver,
not at runtime of the resulting executables.
Well, the spec
On 11/29/2010 02:40 AM, John David Anglin wrote:
I have experienced a number of problems with the new bugzilla. It
seems "Reload current page" doesn't consistently update all fields
(e.g., Target Milestone). As a result, entering new comments, etc,
can corrupt fields that haven't been updated.
@need 800 (all suggested by Ralf); add one-line description to the math
functions
Build on x86-64-linux.
OK for the trunk?
Tobias
2010-11-30 Tobias Burnus
PR fortran/46543
* LICENCES: Add.
* configure.ac: Add texinfo checks.
* Makefile.am: Handle .texi documentation
Joseph S. Myers wrote:
On Tue, 30 Nov 2010, Tobias Burnus wrote:
[-> http://gcc.gnu.org/ml/fortran/2010-11/msg00413.html ]
This is a follow up / rediff to my previous patch at
http://gcc.gnu.org/ml/fortran/2010-11/msg00339.html, incorporating the
comments by Ralf and Matthias.
I think
Hello,
given that the has been quite some libquadmath-related configure work:
Are there still build problems due to link tests if one cross-builds for
bare-iron targets? Or not? (Cf. PR 46520)
If so, I would start to tackle them next.
(As work around, one can now use --disable-libquadmath; h
On 12/13/2010 07:27 PM, Thomas Klein wrote:
It's not clear to me at which point the FSF is trusting an individual
(or organization or company) and why it is mistrusting an individual per
default.
My understanding is that the FSF wants to own the code completely,*
which allows it to re-license
Joel Sherrill wrote:
I was experimenting with adding microblaze-rtems*
and got this error:
>
checking for sqrtl in -lm... configure: error: Link tests are not
allowed after GCC_NO_EXECUTABLES.
make[1]: *** [configure-target-libquadmath] Error 1
I am puzzled: While this issue existed, it shoul
Hello,
I just got the following error message send by bugzilla / GCC's commit
script handler:
Can't locate mro.pm in @INC (@INC contains: . lib/i386-linux-thread-multi lib
CODE(0x958f8b4) /usr/lib/perl5/5.8.5/i386-linux-thread-multi
/usr/lib/perl5/5.8.5 /usr/lib/perl5/site_perl/5.8.5/i386-
On 01/26/2011 12:05 PM, Frédéric Buclin wrote:
Le 26. 01. 11 11:29, Tobias Burnus a écrit :
Can't locate mro.pm in @INC
mro.pm is part of the core code of Perl since version 5.9.5. So it's not
available here as sourceware has Perl 5.8.5 installed. Where is this
script located? And d
---
Mentor Graphics (Deutschland) GmbH, Arnulfstrasse 201, 80634 München
Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Frank
Thürauf
commit 5d3ef9189a7c57679b5fb06e51c90479df0548b0
Author: Tobias Burnus
Date: Sun May 23 11:56:39 2021 +0200
fortran/intrinsic.texi: U
201, 80634 München
Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Frank
Thürauf
commit 2044a3e3e8343d047344523a1cca98309ce68fdc
Author: Tobias Burnus
Date: Tue May 25 09:17:07 2021 +0200
fortran/intrinsic.texi: Fix copy'n'paste errors and typos
g
Hello,
On 13.05.21 13:45, Martin Liška wrote:
On 4/1/21 3:30 PM, Martin Liška wrote:
That said, I'm asking the GCC community for a green light before I
invest
more time on it?
So far, I've received just a small feedback about the transition. In
most cases positive.
[1] https://splichal.eu/scr
On 07.06.21 15:28, Martin Liška wrote:
* I note that we write before the argument index, that those are
without -/-- prefix
but that's not true. Something to fix after the conversation.
Can you please show me a few examples of it?
* https://splichal.eu/scripts/sphinx/gfortran/_build/html
On 10.06.21 08:17, Martin Liška wrote:
Yes, we currently only support automatic extraction from comments from
test-cases.
How does your commit title look like? Note that we require bugzilla
components
being part of PR entry, which is not commonly used in git titles due
to length
limitation.
On
On 10.06.21 10:07, Martin Liška wrote:
On 6/10/21 8:35 AM, Tobias Burnus wrote:
One options would be to require a 'PR /' line if there is
'PRn+' in the commit title, rejecting the commit otherwise.
Quite interesting idea! Are you willing to prepare a patch for it?
D
On 10.06.21 16:55, Martin Sebor via Gcc wrote:
I'm a little lost as to what's being changed, and, truth be told,
what exactly the current "right" format is. Where are the PRn
strings recognized as special?
For my version of the patch at least, which is
https://gcc.gnu.org/pipermail/gcc-pat
On 18.06.21 11:32, Richard Earnshaw via Gcc wrote:
On 17/06/2021 18:21, Jakub Jelinek wrote:
mklog as is doesn't fill in the details (descriptions of the changes
to each function etc.), nor is realiable in many cases, and with Jason's
recent change just fills in the first and last part of the fi
On 18.06.21 13:10, Jonathan Wakely wrote:
On Fri, 18 Jun 2021 at 12:05, Tobias Burnus wrote:
PR c++/12394 - internal compiler error: in write_type, at cp/mangle.c:1517
PR fortran/100123 - -ftree-fre gives incorrect result in subroutine with array
declared as length 1
PR c++/12394
On 18.06.21 16:41, Jason Merrill wrote:
* Being able to specify the PR numbers on the command line in addition
(currently, they are only extracted from the testsuite patches)
This bit seems unnecessary to me, since we want the commit to include
tests that identify the PR.
I full h
On 17.06.21 02:17, Martin Sebor via Gcc wrote:
@@ -147,6 +152,12 @@ def generate_changelog(data, no_functions=False,
fill_pr_titles=False):
# Extract PR entries from newly added tests
if 'testsuite' in file.path and file.is_added_file:
+name = os.path.basename(fi
On 21.06.21 10:09, Martin Liška wrote:
$ pytest test_mklog.py
FAILED test_mklog.py::TestMklog::test_sorting - AssertionError: assert
'\n\tPR 50209...New test.\n\n' == 'gcc/ChangeLo...New test.\n\n'
Aha, missed that there is indeed a testsuite - nice!
$ flake8 mklog.py
mklog.py:187:23: Q000 Rem
for ignoring dir1 and bug1.
Tobias
-
Mentor Graphics (Deutschland) GmbH, Arnulfstrasse 201, 80634 München
Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Frank
Thürauf
commit edf0c3ffb59d75c11e05bc722432dc554e275c72
Author: Tobias Burnus
Date: Mon Jun
Hello,
On 22.06.21 09:30, Martin Liška wrote:
There's a patch candidate that comes up with a wrapper for 'git
commit-mklog' alias.
Using my patch, one can do:
$ git commit-mklog -a -b 12345,
Thoughts?
What about '-p' – to fetch the data from GCC Bugzilla? I do note that
'git commit ' supports
Hi all, hi Thomas (2x), hi Sandra,
On 16.07.21 09:52, Thomas Koenig via Fortran wrote:
The part of the patch to add tests for this goes on top of my base
TS29113 testsuite patch, which hasn't been reviewed or committed yet.
It is my understanding that it is not gcc policy to add xfailed test
c
Hi,
On 01.12.21 19:35, Martin Jambor wrote:
On Tue, Nov 30 2021, Mohamed Atef wrote:
Where is the variable of the OpenMP version defined?
The GCC code itself does not make a difference, contrary to
C/C++/Fortran which have -std=
OpenMP 4.5 (also known as 201511) is fully supported (minus
On 15.12.21 12:39, Jonathan Wakely via Gcc wrote:
Iain pointed out a drawback of not having the regression info in the
Summary. Currently it does draw your attention when looking at the
results of a bugzilla search. Andrew noted that bug aliases are
automatically added to the summary, e.g. https
Dear Mikel,
thanks for the example. I have now filled a tracking issue at
https://gcc.gnu.org/PR103988.
Currently, GCC only supports OpenACC 2.6.
As GCC mainline is in feature-freeze Stage 3, this feature will surely
miss GCC 12, unfortunately.
At the moment, the OpenACC work is mostly focusin
Hi Jakub, hello all,
let's start with a list of smaller patches, which are pending review
but each of them should be relatively quickly approvable. Some are really
tiny and obvious bug fixes - others are a bit larger but still smallish:
* [Patch] OpenMP: Fix use_device_{addr,ptr} with in-data-sha
Hi Mohamed,
On 19.05.22 03:39, Mohamed Atef via Gcc wrote:
Should I commit to devel/omp/gcc-11 branch?
Short answer – no.
Longer answer:
First, devel/omp/gcc-11 (alias OG11) is old – base on GCC 11 and you are
targeting
mainline alias GCC 13. Thus, developing against an old version does not
Hi all,
this seems to be a very recent regression: https://gcc.gnu.org/wiki/ is
currently only limited usable.
Looking at the browser console, the problem is:
GET https://gcc.gnu.org/moin_static1910/common/js/common.js[HTTP/2 404
Not Found 131ms]
GEThttps://gcc.gnu.org/moin_static1910/modern/c
Hi,
On 15.12.22 21:31, Grosse-Bley, Paul Leonard wrote:
I just ran into the issue that `#pragma omp simd` does not work on C++ iterator
loops (godbolt).
From going through the specifications I understand that this restriction was
part of 4.5 and 5.0, but was dropped with 5.1.
I assume that i
Hello,
welcome to the GCC/gfortran community.
On 08.03.23 14:02, Martin Jambor wrote:
On Sat, Mar 04 2023, Priyabrata Mondal via Gcc wrote:
I want to
participate in Google Summer of Code 2023 by contributing to the *Fortran –
DO CONCURRENT* project, an implementation of loop that executes
conc
Hi Shreyash,
On 21.03.23 12:45, Shreyash Pawar via Gcc wrote:
I am interested in gsoc and I know cpp language
See https://gcc.gnu.org/wiki/SummerOfCode for project ideas. I helps to
think about a certain project and to get familiar with GCC.
In particular, please read "Before you apply".
Tha
Hi Adi,
On 31.03.23 14:35, Prasad, Adi wrote:
Rework lto-wrapper so that if the separate host process target is
enabled, it finds and calls a mkoffload for the host architecture
instead of looking for an offloading compiler’s mkoffload; then write
a mkoffload tool for a separate host process.
Hi all,
the following works for me. I have only tried a normal build (where it
does silence the same warning) and not an LTO build and I just believed
the comment - see attached patch. Comments?
On 28.09.23 08:25, Richard Biener via Fortran wrote:
This particular place in libgfortran has
/
Hi Tom,
On 21.11.23 11:32, Hamish Baxter via Gcc wrote:
I am a current Computer Science student who enjoys C programming with an
interest in learning compilers, and am looking to contribute to an
open source project.
I am not sure exactly where to start or how it works: perhaps testing /
techni
(Un)subscribing from mailing lists:
Go to https://gcc.gnu.org/lists.html
Click on any list, at the top, click on "more information about this
list." and on the bottom you find: "Unsubscribe or edit options".
For gcc-patches, that's https://gcc.gnu.org/mailman/options/gcc-patches
Or sent an ema
Hello Mohamed,
Jakub Jelinek wrote:
Mohamed Atef via Gcc wrote:
I am still interested in working on OMPD. Are there any plans for OMPD,
soon?
I think no one is currently working on OMPD or is planning to do so in
the near future - but support for OMPD would be surely nice.
It is surely to
Hi Janne,
Janne Blomqvist wrote:
back when I was active I did think about this
issue. IMHO the best of my ideas was to convert these into C++
templates.
I think this will work – but we have to be super careful:
With C++, there is the problem that we definitely do not want to add
dependency o
I am forwarding it as I only saw it on the fortran@gcc but not on the
gcc@ list.
Original Message
Subject:IMPORTANT: sourceware.org hardware migration, MARCH 18..22
Date: Tue, 12 Mar 2013 11:36:04 -0400 (EDT)
From: Frank Ch. Eigler
Hi -
Please be aware that **ne
John Franklin wrote:
"cpmpilation"
probably meant "compilation"
Thanks for the report. I have fixed it with the attached patch.
Tobias
Index: gcc-4.8/changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.8/changes.html,v
retri
Foone Turing wrote:
This page: http://gcc.gnu.org/gcc-4.8/
under "release history" says GCC 4.8 was released on March 22, 2012.
This should be 2013, not 2012.
Thanks for the report! I have corrected it now.
Tobias
Index: index.html
==
Kiefmann Bernhard wrote:
My name is Bernhard Kiefmann and I'm writing my Master's thesis with the topic "the
suitability of the GNU C compiler used in safety-related areas". The first problem
with this is that I have to check if the compiler met the requirements of the
international standard I
Thorsten Glaser wrote:
“We will periodically pick a stable version of GCC, and require that that
version of GCC be able to build all versions of GCC up to and including
the next stable version. [...]
Which version has currently been picked, and where can such information
reliably (thinking of a p
In a nutshell:
* GCC has been accepted for GSoC
* Potential mentors: Please register
* April 22 to May 3: Students application period
* May 27: Announcement of the accepted projects
* June 17 to September: GSoC coding period
We are gland to announce that GCC has been accepted as organization for
Ghassan Shobaki wrote:
We are currently working on a research
project on instruction scheduling for low power (experimenting with
different algorithms for minimizing switching power) and would like to
find out if GCC already has such a scheduler and how it can be enabled, so that
we can experime
Hello Iyer,
Iyer, Balaji V wrote:
The fortran compiler (f951) seem to hang even for a simple hello world program
in GCC. This is causing the whole gcc build process to hang at the following
line:
checking for x86_64-unknown-linux-gnu-gfortran...
/export/users/gcc-svn/b-cilkplus-gcc/./gcc/gf
Am 29.04.2013 22:14, schrieb Scott Baldwin:
Just downloaded 4.8.0 from one of your mirror sites listed at
[http://gcc.gnu.org/mirrors.html] and would like to verify the file with
GPG.
Your site says "The archives there will be signed by one of the following
GnuPG keys...", but I see no .sig/.asc
guray.ozen wrote:
I thought gcc tasks/threads waiting too much on the idle than intel
compiler's threads.
Regarding busy waits, you could try to tune the values of the
GOMP_SPINCOUNT environment variable. Search for "@node GOMP_SPINCOUNT"
in
http://gcc.gnu.org/viewcvs/gcc/branches/gomp-4_0-b
Evgeny Gavrin wrote:
What do you think about support of OpenACC 1.0
(http://www.openacc-standard.org/) in gcc?
I like the idea - though, I wonder whether OpenMP 4.0's "target"* would
be the better choice as it looks a bit more flexible and better defined.
(Conceptually, they are very similar;
Richard Biener wrote:
We're going to look at supporting HSA from GCC (which would make it
more or less trivial to also target openCL I think)
For the friends of link-time optimization (LTO):
Unless I missed some fine point in OpenACC and OpenMP's target, they
only work with directives which a
Jakub Jelinek wrote:
[Fallback generation of CPU code]
If one uses the OpenMP 4.0 accelerator pragmas, then that is the required
behavior, if the code is for whatever reason not possible to run on the
accelerator, it should be executed on host [...]
(I haven't checked, but is this a compile time
guray.ozen wrote:
I applied gsoc for openMP taks scheduling and my advice may cover
taskyield facility. Currently i have some idea for taskyield. i think
i can add something. Therefore i wonder GCC mentor related about
openMP was announced? or should i wait until "student acceptance"?
You have
Hi Steve,
Steve Ellcey wrote:
I have a question about the libgfortran configure script. I am trying to
build the fortran language for the mips-mti-elf target (which is built with
newlib) and as part of the configure script for libgfortran it is trying to
check for localtime_r and other function
Andrew MacLeod wrote:
* Quite a lot of target interfaces would be used by the front ends
specifically for defining macros for building target libraries only; see
the "probably predefine macros if -fbuilding-libgcc in most cases"
list on
that wiki page. (Thus, given a clean separation of target-s
Martin Reinecke wrote:
>
> The attached testcase requires gcc and gfortran, as well as a JDK
> installation. When running "make" with gcc/gfortran 4.7.2 and
> Oracle JDK 1.7, a single call to JNI_CreateJavaVM() changes the
> behaviour of subsequent READ statements in the Fortran code,
> depending
Jeff Law wrote:
On 07/22/2013 03:07 AM, Evgeny Gavrin wrote:
Earlier we (Samsung R&D Institute Rus) proposed to implement OpenACC for
GCC: http://gcc.gnu.org/ml/gcc/2013-05/msg00060.html
We got our assignment form, now.
Great! I am looking forward to the implementation!
I assume that you only
Dear all,
sometimes it can be useful to annotate loops for better vectorization,
which is rather independent from parallelization.
For vectorization, GCC has [0]:
a) Cilk Plus's #pragma simd [1]
b) OpenMP 4.0's #pragma omp simd [2]
Those require -fcilkplus and -fopenmp, respectively, and activ
Bob Fischer wrote:
It would be useful if one could declare assumed shape arrays in Fortran, and
then pass them to C/C++. The GNU Fortran documentation claims this is not
normally possible in Fortran 2003. However, I have developed (and use daily) a
standards-compliant way to do it.
Well, y
Gerald Pfeifer wrote:
To make it easier to reproduce builds of software and entire GNU/Linux
distributions, RMS had the idea of adding a warning to GCC that warns
about the use of __DATE__ and __TIME__.
I assume that he also likes to have a warning for __TIMESTAMP__.
I was thinking a new warn
Tobias Burnus wrote:
Gerald Pfeifer wrote:
To make it easier to reproduce builds of software and entire GNU/Linux
distributions, RMS had the idea of adding a warning to GCC that warns
about the use of __DATE__ and __TIME__.
I assume that he also likes to have a warning for __TIMESTAMP__.
I
FX wrote:
I’m building with binutils 2.17.50.0.6, which is a bit old but I cannot find
any mention of needing later binutils on the installation notes.
Is bootstrap broken, or am I missing something?
Second build, this time with trunk binutils. Still fails in libsanitizer at
stage1, this time
Güray Özen wrote:
I came across a news about gcc will support OpenACC/OpenMP target
directive. How can i download this version?
Well, the support is at an early stage, targetting several different
backends. The work is done by several teams and, hence, not always very
well coordinated. I thin
Hello,
motivated by the recent MPC 1.0.2 announcement, I looked at
./contrib/download_prerequisites and also at
ftp://gcc.gnu.org/pub/gcc/infrastructure/ to see which versions are
offered there.
Question: Would it make sense to place newer versions into
infrastructure and update ./contrib/d
Renato Golin wrote:
On 15 February 2014 19:26, Jakub Jelinek wrote:
GCC supports #pragma GCC ivdep/#pragma simd/#pragma omp simd, the last one
can be used without rest of OpenMP by using -fopenmp-simd switch.
Does the simd/omp have control over the tree vectorizer? Or are they
just flags for
ng-removal patch.
OK for the trunk?
Regarding invoke.texi: It had (nearly) the same @menu twice, once under
@chapter where it belongs to and once under a @section where it doesn't.
Tobias
2014-03-29 Tobias Burnus
PR other/59055
* doc/bugreport.texi (Bugs): Remove nodes pointin
*PING*
Tobias Burnus wrote:
H.J. Lu wrote:
On Fri, Mar 28, 2014 at 12:41 PM, Mike Stump
wrote:
Since we are nearing release, I thought I'd mention I see:
../../gcc/gcc/doc/invoke.texi:1114: warning: node next `Overall
Options' in menu `C Dialect Options' and in sectioni
* PING *
Tobias Burnus wrote:
*PING*
Tobias Burnus wrote:
H.J. Lu wrote:
On Fri, Mar 28, 2014 at 12:41 PM, Mike Stump
wrote:
Since we are nearing release, I thought I'd mention I see:
../../gcc/gcc/doc/invoke.texi:1114: warning: node next `Overall
Options' in menu `C Dialect Op
Am 18.02.2012 11:36, Mads Jensen wrote:
I've noticed that not all strings in the function
gfc_ascii_statement
in fortran/parse.c are supported by gettext with the _()-macro. Is there
a reason for this?
Well, usually it is not a good idea to translate statement names like
WRITE, SELECT TYPE etc
Richard Henderson wrote:
> So, I've got something put together. I think it should be fairly scalable.
[...]
> Comments welcome. Andrew, didn't you say you had some code as well, but
> didn't want to argue with autofoo?
I think Andrew's version is attached to
http://gcc.gnu.org/wiki/Atomic/GCCM
Torvald Riegel wrote:
On Wed, 2012-04-11 at 11:24 +0200, Richard Guenther wrote:
> Honestly I care 1000 times more for existing GCC developers. Before
> new programmers will have an easier time with GCC_existing_ GCC
> developers will have to spend at least two GCC release cycles (that's
>
PERRONNET Alain wrote:
My program and subroutines are mainly written in fortran 77 with blanck
common of different sizes.
If the program and subroutines are compiled with the option -g the
load-module is OK.
if the program and subroutines are compiled with the option -O the
execution
of the lo
Ian Lance Taylor wrote:
"Iyer, Balaji V" writes:
Is there a #define in GCC that will turn on only for certain languages?
I am trying to use build_array_ref but it is giving me a undefined reference
for f951. This code that I am trying to use will ONLY execute if we have a
C/C++ cod
On 06/28/2012 07:43 AM, Georg-Johann Lay wrote:
The admin logs look clean now, but the generated documents still didn't
make it to the website, e.g. changes after 2012-05-29 like the
mentioned SVN 188070.
The admin log still shows the following issue for libgomp, cf.
http://gcc.gnu.org/ml/gcca
H.J. Lu wrote:
I saw massive FORTRAN failures on trunk with both SPEC CPU 2006
and GCC FORTRAN testsuite. Is this a known problem? Should I open a bug
report?
I assume that you do not install GCC before you run the test suite – and
that you don't have a GCC installed at the --prefix= location
Gabriel Dos Reis wrote:
A few points to consider:
* relation of __builtin_function_location to C99 (and C++11) __func__
* Do we want to update libcpp to systematically expand __FILE__ to
__builtin_file_location, etc?
If you do so, please make sure that you don't break Fortran,
Am 15.08.2012 18:26, schrieb Gabriel Dos Reis:
On Wed, Aug 15, 2012 at 11:21 AM, Tobias Burnus wrote:
Gabriel Dos Reis wrote:
A few points to consider:
* relation of __builtin_function_location to C99 (and C++11) __func__
* Do we want to update libcpp to systematically expand
David N. Bradley wrote:
I am trying to compile the cactuscode package and can not get past the
error :
Statement order error: declaration after DATA
Somehow the whole is very odd.
a) I tried your program with gfortran 4.1 to 4.8, g95 and g77 - and none
of them prints this error - all comp
Dear all,
I have a question to the GCC build-system experts to make
TARGET_SYSTEM_ROOT available to gfortran (see PR54725); it's required to
have the proper "/usr/include" directory when using CPP.
That's partially cured by the patch below, however, it is not sufficient
as "TARGET_SYSTEM_ROO
Hello Steven,
Steven Bosscher wrote:
Can someone please add a BZ keyword for the C11/C++11 memory model? I
think it would be good to tag missed-optimizations or wrong-code bugs
for the memory model with such a special keyword to have a BZ search
find them quickly.
Adding a keyword is simple, i
Richard Biener wrote:
On Tue, Jan 15, 2013 at 6:46 AM, Uday P. Khedker wrote:
GCC has been building stages 2 and 3 in C++ mode for a while.
The C++ compiler is created anyway since 4.7 and is used to build
stage2+. Starting with GCC 4.8 stage1 requires a C++ host compiler.
In GCC 4.7 you c
Dear all, hello Gerald,
I wonder if we could generate a version-specific page for the online
documentation. I think that should be trivial to maintain and I know at
least one vendor who would use it.
Namely, to place an "index.html" into, e.g.,
http://gcc.gnu.org/onlinedocs/gcc-4.7.2/ which
Gerald Pfeifer wrote:
On Sun, 17 Feb 2013, Tobias Burnus wrote:
I wonder if we could generate a version-specific page for the online
documentation. I think that should be trivial to maintain and I know
at least one vendor who would use it.
If "we" means that you are vo
Gerald Pfeifer wrote:
On Mon, 18 Feb 2013, Tobias Burnus wrote:
How about the following patch? If it is okay, I will add the remaining
index.html for 4.6 and 4.7 and update gcc-4.6/index.html – and then
commit it.
Looks good to me.
Perhaps you can add a note for the release manager how to
Jeffrey Walton wrote:
On Mon, Feb 25, 2013 at 4:51 AM, Richard Biener
wrote:
On Mon, Feb 25, 2013 at 6:20 AM, Chung-Ju Wu wrote:
Don't worry about possible confusion (-Og needs -gN). Document it at
http://gcc.gnu.org/onlinedocs/gcc/Debugging-Options.html#Debugging-Options,
and folks should
Hi,
Torvald Riegel wrote:
will GCC be a mentoring organization for Google Summer of Code this
year?
Well, the application of the organizations only starts in about three
weeks* and which orgs will be participating is only announced on April
8. However, it is very likely that GCC will partici
David Daney wrote:
> The gfortran.dg/optional_dim_2.f90 test has been failing on mipsel-linux
> ever since it was added.
See PR 34387. If you want, you could try the patch posted there.
Tobias
J.C. Pizarro wrote:
2nd. Fortran
4.0.x: I don't know, but one should really not use that version
4,[1-3].x come with incompatible gfortran libraries, which have also
different version numbers: libgfortran.so.1 to libgfortran.so.3.
Minor versions are upward compatible, i.e. programs compiled wi
According to the GCC 4.4 Release Criteria,
http://gcc.gnu.org/gcc-4.4/criteria.html, only C and C++ are primary
languages. And thus only C and C++ regressions can be release critical.
I propose to add Fortran to these languages. Reasons:
- Fortran is relatively widely used; while C/C++ is wide
101 - 200 of 211 matches
Mail list logo
