Re: gcc-7.3.0: ptxas lib_a-hash_func.o, line 11; fatal : Invalid initial value expression

[Thomas Schwinge]

Hi!

On Sat, 24 Feb 2018 17:20:13 +0100, Siegmar Gross 
 wrote:
> today I tried to install gcc-7.3.0 with accelerator support

Thanks for giving that a try and reporting back!

> on my "SUSE Linux Enterprise Server 12.3 (x86_64)" with
> gcc-6.4.0. I used the following commands to download and build
> everything.

Thanks for providing these (but I have not yet reviewed them in detail,
because the problem might be solved already, see below).

> '../../../../../../gcc-7.3.0/newlib/libc/search/'`hash_func.c
> ptxas lib_a-hash_func.o, line 11; fatal   : Invalid initial value expression
> ptxas fatal   : Ptx assembly aborted due to errors
> nvptx-as: ptxas returned 255 exit status
> Makefile:413: recipe for target 'lib_a-hash_func.o' failed
> make[8]: *** [lib_a-hash_func.o] Error 1

Am I right guessing that you're using CUDA 9?  Then it'd most likely be
the issue discussed in  "Update nvptx target
to work with cuda 9".  By now, there has a fix been committed to GCC
trunk, and I assume the same would also work on earlier GCC
releases/branches.

> I was able to build that part for gcc-7.2.0 with the same commands.

Interesting.  Or, maybe you've not been using CUDA 9 in that build?


Grüße
 Thomas

[PATCH] for Re: netgull.com mirror doesn't have gcc release .sig files.

[Gerald Pfeifer]

On Tue, 8 Jul 2014, Richard Biener wrote:
>> The reason you do not see .sig files on our netgull.com mirror is
>> that it mirrors gcc.gnu.org, which does not carry those, whereas
>> ftp.gnu.org and hence its mirrors has them.
>>
>> Richi, Jakub, can you also add those .sig files to the copies on
>> gcc.gnu.org going forward?
> Nothing against that ... can you add an action item to releasing.html 
> please?

Done thusly.

Sorry for the delay (ahem).

Gerald

Index: releasing.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/releasing.html,v
retrieving revision 1.48
diff -u -r1.48 releasing.html
--- releasing.html  17 Jan 2018 13:10:17 -  1.48
+++ releasing.html  23 Feb 2018 07:54:01 -
@@ -60,6 +60,9 @@
 
 Upload the release to ftp.gnu.org.
 
+Ensure that the upload on gcc.gnu.org also comes with
+cryptographic signatures (.sig files).
+
 Increment the version number in gcc/BASE-VER. 
 gcc/DEV-PHASE remains empty. Check the file in.
 

Re: GSoC

[Martin Jambor]

Hi Thejazeto,

I apologize for replying this late, I've been traveling and did not
manage to write to you earlier as a consequence.

On Wed, Feb 21 2018, Thejazeto Lhousa wrote:
> Hello,
>
> I went through the GSoC 2018 idealist and found 'Improving GCC
> Developer Documentation' to be interesting and feasible for me.
> But I am confused because I remember reading somewhere that
> documentation will not be accepted as a valid project for GSoC.
> Can anyone shed some light?

You are right, the rules do not allow documentation-only projects, thank
you very much for pointing this out. As Thomas pointed out, I have
corrected the wiki.

Moreover, I think that writing good internal documentation is actually a
fairly difficult task that is not really suitable for newcomers, because
it often takes quite some knowledge to understand all important caveats.

Nevertheless, if you are really interested in compilers in general and
GCC in particular, please not feel put off by this.  Check out and build
GCC (as described at https://gcc.gnu.org/install/) and experiment with
it a little, you may find it is not actually as hard as it seems.  Feel
free to ask for help here on the mailing list or on our IRC when you get
stuck, we are a friendly bunch that want to help beginners, even though
we are often busy.

If the scope of GCC still intimidates you (but we all struggle with it
sometimes, trust me), consider reaching out to Andi Kleen and discuss
his fuzzer project idea with him (he may tell you what to check out and
experiment with to get the feeling about the task at hand).

Thanks again for notifying us about the documentation and I hope that
you will eventually find a project you will enjoy,

Martin

gcc-7.3.0: ptxas lib_a-hash_func.o, line 11; fatal : Invalid initial value expression

[Siegmar Gross]

Hi,

today I tried to install gcc-7.3.0 with accelerator support
on my "SUSE Linux Enterprise Server 12.3 (x86_64)" with
gcc-6.4.0. I used the following commands to download and build
everything.

setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:/usr/local/cuda/lib64
setenv CUDA_INC_PATH /usr/local/cuda/include
setenv CUDA_LIB_PATH /usr/local/cuda/lib64
set path = ( ${path} /usr/local/cuda/bin )

git clone https://github.com/MentorEmbedded/nvptx-tools
git clone https://github.com/MentorEmbedded/nvptx-newlib

wget ftp://ftp.gwdg.de/pub/misc/gcc/releases/gcc-7.3.0/gcc-7.3.0.tar.xz
tar xf gcc-7.3.0.tar.xz
cd gcc-7.3.0
ln -s ../nvptx-newlib/newlib newlib
cd ..

mkdir make_nvptx-tools
cd make_nvptx-tools
../nvptx-tools/configure --prefix=/usr/local/gcc-7.3.0 \
  |& tee log.configure
make |& tee log.make
make install |& tee log.make-install
cd ..

mkdir gcc-7.3.0_build
cd gcc-7.3.0_build
../gcc-7.3.0/configure --prefix=/usr/local/gcc-7.3.0 \
  --target=nvptx-none \
  --enable-as-accelerator-for=x86_64-pc-linux-gnu \
  --with-build-time-tools=/usr/local/gcc-7.3.0/nvptx-none/bin \
  --disable-sjlj-exceptions \
  --with-newlib \
  --enable-newlib-io-long-long \
  --enable-languages=c,c++,fortran,lto \
  |& tee log.configure
make |& tee log.make


Unfortunately, "make" breaks with the following error.

loki gcc-7.3.0_build 117 tail -31 log.make
/export2/src/gcc-7.3.0/gcc-7.3.0_build/./gcc/xgcc -B/export2/src/gcc-7.3.0/gcc-7.3.0_build/./gcc/ -nostdinc 
-B/export2/src/gcc-7.3.0/gcc-7.3.0_build/nvptx-none/mgomp/newlib/ -isystem /export2/src/gcc-7.3.0/gcc-7.3.0_build/nvptx-none/mgomp/newlib/targ-include -isystem 
/export2/src/gcc-7.3.0/gcc-7.3.0/newlib/libc/include -B/usr/local/gcc-7.3.0/nvptx-none/bin/ -B/usr/local/gcc-7.3.0/nvptx-none/lib/ -isystem 
/usr/local/gcc-7.3.0/nvptx-none/include -isystem /usr/local/gcc-7.3.0/nvptx-none/sys-include  -mgomp -DPACKAGE_NAME=\"newlib\" -DPACKAGE_TARNAME=\"newlib\" 
-DPACKAGE_VERSION=\"2.1.0\" -DPACKAGE_STRING=\"newlib\ 2.1.0\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -I. -I../../../../../../gcc-7.3.0/newlib/libc/search 
-DMALLOC_PROVIDED -DMISSING_SYSCALL_NAMES -fno-builtin  -g -O2  -mgomp -c -o lib_a-hash_buf.o `test -f 'hash_buf.c' || echo 
'../../../../../../gcc-7.3.0/newlib/libc/search/'`hash_buf.c
/export2/src/gcc-7.3.0/gcc-7.3.0_build/./gcc/xgcc -B/export2/src/gcc-7.3.0/gcc-7.3.0_build/./gcc/ -nostdinc 
-B/export2/src/gcc-7.3.0/gcc-7.3.0_build/nvptx-none/mgomp/newlib/ -isystem /export2/src/gcc-7.3.0/gcc-7.3.0_build/nvptx-none/mgomp/newlib/targ-include -isystem 
/export2/src/gcc-7.3.0/gcc-7.3.0/newlib/libc/include -B/usr/local/gcc-7.3.0/nvptx-none/bin/ -B/usr/local/gcc-7.3.0/nvptx-none/lib/ -isystem 
/usr/local/gcc-7.3.0/nvptx-none/include -isystem /usr/local/gcc-7.3.0/nvptx-none/sys-include  -mgomp -DPACKAGE_NAME=\"newlib\" -DPACKAGE_TARNAME=\"newlib\" 
-DPACKAGE_VERSION=\"2.1.0\" -DPACKAGE_STRING=\"newlib\ 2.1.0\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -I. -I../../../../../../gcc-7.3.0/newlib/libc/search 
-DMALLOC_PROVIDED -DMISSING_SYSCALL_NAMES -fno-builtin  -g -O2  -mgomp -c -o lib_a-hash_func.o `test -f 'hash_func.c' || echo 
'../../../../../../gcc-7.3.0/newlib/libc/search/'`hash_func.c

ptxas lib_a-hash_func.o, line 11; fatal   : Invalid initial value expression
ptxas fatal   : Ptx assembly aborted due to errors
nvptx-as: ptxas returned 255 exit status
Makefile:413: recipe for target 'lib_a-hash_func.o' failed
make[8]: *** [lib_a-hash_func.o] Error 1
make[8]: Leaving directory 
'/export2/src/gcc-7.3.0/gcc-7.3.0_build/nvptx-none/mgomp/newlib/libc/search'
Makefile:635: recipe for target 'all-recursive' failed
make[7]: *** [all-recursive] Error 1
make[7]: Leaving directory 
'/export2/src/gcc-7.3.0/gcc-7.3.0_build/nvptx-none/mgomp/newlib/libc'
Makefile:627: recipe for target 'all-recursive' failed
make[6]: *** [all-recursive] Error 1
make[6]: Leaving directory 
'/export2/src/gcc-7.3.0/gcc-7.3.0_build/nvptx-none/mgomp/newlib'
Makefile:450: recipe for target 'all' failed
make[5]: *** [all] Error 2
make[5]: Leaving directory 
'/export2/src/gcc-7.3.0/gcc-7.3.0_build/nvptx-none/mgomp/newlib'
Makefile:1188: recipe for target 'multi-do' failed
make[4]: *** [multi-do] Error 1
make[4]: Leaving directory 
'/export2/src/gcc-7.3.0/gcc-7.3.0_build/nvptx-none/newlib'
Makefile:1104: recipe for target 'all-multi' failed
make[3]: *** [all-multi] Error 2
make[3]: Leaving directory 
'/export2/src/gcc-7.3.0/gcc-7.3.0_build/nvptx-none/newlib'
Makefile:450: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory 
'/export2/src/gcc-7.3.0/gcc-7.3.0_build/nvptx-none/newlib'
Makefile:11097: recipe for target 'all-target-newlib' failed
make[1]: *** [all-target-newlib] Error 2
make[1]: Leaving directory '/export2/src/gcc-7.3.0/gcc-7.3.0_build'
Makefile:873: recipe for target 'all' failed
make: *** [all] Error 2
loki gcc-7.3.0_build 118

I was able to build that part for gcc-7.2.0 with the same commands.

/export2/src/gcc-7.2.0/gcc-7.2.0_build/./gcc/xgcc 
-B/exp

Re: GSoC

[Thejazeto Lhousa]

Thank you for the clarification.

On Feb 24, 2018 4:25 PM, "Thomas Schwinge"  wrote:

> Hi!
>
> On Wed, 21 Feb 2018 21:35:35 +0530, Thejazeto Lhousa 
> wrote:
> > I went through the GSoC 2018 idealist
>
> Thanks for your interest!
>
> > found 'Improving GCC
> > Developer Documentation' to be interesting and feasible for me.
> > But I am confused because I remember reading somewhere that
> > documentation will not be accepted as a valid project for GSoC.
> > Can anyone shed some light?
>
> You're correct: per , 1.26
> "Project", "Projects do not include projects for documentation only".
> Martin has now removed that item from the Project Ideas list,
> .
>
>
> Grüße
>  Thomas
>

Re: GSoC

[Thomas Schwinge]

Hi!

On Wed, 21 Feb 2018 21:35:35 +0530, Thejazeto Lhousa  
wrote:
> I went through the GSoC 2018 idealist

Thanks for your interest!

> found 'Improving GCC
> Developer Documentation' to be interesting and feasible for me.
> But I am confused because I remember reading somewhere that
> documentation will not be accepted as a valid project for GSoC.
> Can anyone shed some light?

You're correct: per , 1.26
"Project", "Projects do not include projects for documentation only".
Martin has now removed that item from the Project Ideas list,
.


Grüße
 Thomas