[Bug target/38326] New: [4.3 regression] libjava build failure on ia64-linux-gnu

[Bug target/38326] New: [4.3 regression] libjava build failure on ia64-linux-gnu

[doko at ubuntu dot com]

seen with 4.3 branch 20081115 20081122

/home/packages/gcc/gcj-4.3-4.3.2/build/ia64-linux-gnu/libjava$
/home/packages/gcc/gcj-4.3-4.3.2/build/gcc/gcj
-B/home/packages/gcc/gcj-4.3-4.3.2/build/ia64-linux-gnu/libjava/
-B/home/packages/gcc/gcj-4.3-4.3.2/build/gcc/ -funwind-tables -fclasspath=
-fbootclasspath=../../../src/libjava/classpath/lib --encoding=UTF-8
-Wno-deprecated -fbootstrap-classes -findirect-dispatch -fno-indirect-classes
-fsource-filename=/home/packages/gcc/gcj-4.3-4.3.2/build/ia64-linux-gnu/libjava/classpath/tools/all-classes.lst
-g -O2 -MT classpath/tools/libgcj_tools_la-tools.lo -MD -MP -MF
classpath/tools/.deps/libgcj_tools_la-tools.Tpo -c classpath/tools/tools.zip 
-fPIC -o classpath/tools/.libs/libgcj_tools_la-tools.o               
jc1: internal compiler error: in java_parse_file, at java/jcf-parse.c:1957
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcj-4.3/README.Bugs> for instructions.


-- 
           Summary: [4.3 regression] libjava build failure on ia64-linux-gnu
           Product: gcc
           Version: 4.3.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: doko at ubuntu dot com
GCC target triplet: ia64-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38326

[Bug target/38326] [4.3 regression] libjava build failure on ia64-linux-gnu

[ebotcazou at gcc dot gnu dot org]

------- Comment #1 from ebotcazou at gcc dot gnu dot org  2008-11-30 10:52 -------
Do you have local changes?  This works fine on SuSE:
  http://gcc.gnu.org/ml/gcc-testresults/2008-11/msg02676.html


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38326

[Bug target/38326] [4.3 regression] libjava build failure on ia64-linux-gnu

[doko at ubuntu dot com]

------- Comment #2 from doko at ubuntu dot com  2008-12-01 11:16 -------
afaics no ia64 specific changes besides the proposed patch for pr27880 to
configure --with-system-libunwind.

trunk fails as well, build log at
https://launchpad.net/ubuntu/+source/gcc-snapshot/20081130-0ubuntu1/+build/800751

no relevant patches applied.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38326

[Bug target/38326] [4.3/4.4 regression] libjava build failure on ia64-linux-gnu

[ebotcazou at gcc dot gnu dot org]

------- Comment #3 from ebotcazou at gcc dot gnu dot org  2008-12-09 18:32 -------
Now on to this one. :-)  Is 20081115 the date of the first failure? 08 was
fine?

There are test results for IA-64/Linux (suse-linux and unknown-linux) both
4.3.3
and 4.4.0 posted on the gcc-testresults on a daily basis.


-- 

ebotcazou at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ebotcazou at gcc dot gnu dot
                   |                            |org
             Status|UNCONFIRMED                 |WAITING


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38326

[Bug target/38326] [4.3/4.4 regression] libjava build failure on ia64-linux-gnu

[steven at gcc dot gnu dot org]

------- Comment #4 from steven at gcc dot gnu dot org  2008-12-09 18:53 -------
I have had no trouble bootstrapping 4.4 on ia64-unknown-linux-gnu (Debian) in
the last two weeks.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38326

[Bug target/38326] [4.3/4.4 regression] libjava build failure on ia64-linux-gnu

[doko at ubuntu dot com]

------- Comment #5 from doko at ubuntu dot com  2008-12-09 19:50 -------
which versions of binutils/glibc are used? for debian these are binutils-2.18.1
and glibc-2.7.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38326

[Bug target/38326] [4.3/4.4 regression] libjava build failure on ia64-linux-gnu

[pinskia at gcc dot gnu dot org]

-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |4.3.3


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38326

[Bug target/38326] [4.3/4.4 regression] libjava build failure on ia64-linux-gnu

[jakub at gcc dot gnu dot org]

------- Comment #6 from jakub at gcc dot gnu dot org  2009-01-05 11:54 -------
Can you reproduce it with vanilla trunk?  I've certainly bootstrapped/regtested
the trunk on ia64-linux several times recently.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38326

[Bug target/38326] [4.3/4.4 regression] libjava build failure on ia64-linux-gnu

[doko at ubuntu dot com]

------- Comment #7 from doko at ubuntu dot com  2009-01-05 18:33 -------
> Can you reproduce it with vanilla trunk?

yes.

now, building with binutils 2.18 and glibc-2.7 lets the build succeed, building
with binutils-2.19 and glibc-2.9 (Ubuntu jaunty) lets the build fail. I'm
trying next to update just one of binutils and glibc.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38326

[Bug target/38326] [4.3/4.4 regression] libjava build failure on ia64-linux-gnu

[arthur dot loiret at gmail dot com]

------- Comment #8 from arthur dot loiret at gmail dot com  2009-01-09 09:15 -------
I can reproduce it on Debian unstable. The problem is in Debian's fastjar on
ia64:

(cd classes; \
        /usr/bin/fastjar cf ../tools.zip `find . -name .svn -prune -o -type f
-print`; \
        cd ..)
/bin/sh: line 2:  7749 Segmentation fault      /usr/bin/fastjar cf ../tools.zip
`find . -name .svn -prune -o -type f -print`
(cd asm; \
        /usr/bin/fastjar uf ../tools.zip `find . -name .svn -prune -o -type f
-print`; \
        cd ..)
/usr/bin/fastjar: ../tools.zip: can't seek file


This results an empty tools.zip and causes the ICE. fastjar is currently
compiled with -O2, with it compiled with -O0 the build successes. Matthias,
does a simple "fastjar cf a.zip" segfaults for you ?


-- 

arthur dot loiret at gmail dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |arthur dot loiret at gmail
                   |                            |dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38326

[Bug target/38326] [4.3/4.4 regression] libjava build failure on ia64-linux-gnu

[doko at ubuntu dot com]

------- Comment #9 from doko at ubuntu dot com  2009-01-09 13:32 -------
yes, fastjar is segfaulting for the test

  fastjar -cf conftest.jar <existing file>

seen as well, when building with current 4.1 and 4.2 branches. a fastjar built
with 3.4.6 works ok.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38326

[Bug target/38326] [4.3/4.4 regression] libjava build failure on ia64-linux-gnu

[jakub at gcc dot gnu dot org]

------- Comment #10 from jakub at gcc dot gnu dot org  2009-01-09 14:30 -------
This is an obvious bug in fastjar-0.97:

ub4
unix2dostime (time_t *unix_time)
{
  struct tm *ltime = localtime (unix_time);
  int year = ltime->tm_year - 80;
...
}

int make_manifest(int jfd, const char *mf_name, int updating)
{
  time_t current_time;
  size_t nlen;   /* length of file name */
  int mod_time; /* file modification time */
  struct zipentry *ze;

  mod_time = unix2dostime(&current_time);

  /* If we are creating a new manifest, create a META-INF directory entry */
  if (0 == updating) {
    nlen = 9;  /* trust me on this one */

    memset((file_header + 12), '\0', 16); /*clear mod time, crc, size fields*/

    current_time = time(NULL);
    if(current_time == (time_t)-1)
      exit_on_error("time");
...

current_time is uninitialized when calling unix2dostime and depending on what
kind of garbage it contains, localtime either returns some randomly filled
struct tm pointer, or NULL.  If it returns NULL (and it doesn't bother checking
for non-NULL returned value), it segfaults.

fastjar-0.96 and earlier in make_manifest always did current_time = time
(NULL);
etc. before calling unix2dostime.


-- 

jakub at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
         Resolution|                            |INVALID


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38326