Hi,
the FSF is located in Free Software Foundation, 31 Milk Street, #960789,
Boston, MA 02196 USA.
Older GPL licenses contained that mail address ("51 Franklin Street,
Fifth Floor, Boston, MA 02110-1301 USA"), which is no longer valid.
Therefore, the FSF updated their licenses to point only
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
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
(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
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
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 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 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
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,
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
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 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 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
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
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
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
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
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
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
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
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 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 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 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 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 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 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 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
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
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
---
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
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
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 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
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,
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 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
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"
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 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
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 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
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
-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
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
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
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 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
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
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
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
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
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
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 "***
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
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
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
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
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
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
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
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
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
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 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 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 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.
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
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
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
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
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
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
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
* 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
*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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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;
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
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
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
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
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
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
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
1 - 100 of 211 matches
Mail list logo
