[Bug ada/37034] /bin/sh: line 1: 26087 Aborted (core dumped) ./xsinfo ../../sinfo.h

[charlet at adacore dot com]

--- Comment #3 from charlet at adacore dot com  2008-08-07 06:41 ---
Subject: Re:  /bin/sh: line 1: 26087 Aborted  (core dumped)
./xsinfo ../../sinfo.h

> > > mkdir -p ada/bldtools/einfo
> > > (cd ada/bldtools/sinfo && gnatmake -q xsinfo && ./xsinfo ../../sinfo.h )
> > > rm -f ada/bldtools/einfo/einfo.ads ada/bldtools/einfo/einfo.adb
> > > ada/bldtools/einfo/xeinfo.adb
> > > cp -p ../../gcc/gcc/ada/einfo.ads ../../gcc/gcc/ada/einfo.adb
> > > ../../gcc/gcc/ada/xeinfo.adb ada/bldtools/einfo
> > > (cd ada/bldtools/einfo && gnatmake -q xeinfo && ./xeinfo ../../einfo.h )
> > > /bin/sh: line 1: 26087 Aborted (core dumped) ./xsinfo
> > 
> > Sounds like your base Ada compiler may be corrupted, since the line above
> > calls 'gnatmake', it does not use the newly built compiler.
> 
> I belive it is xeinfo that's dropping core.  This occurs in stage2.

Right, and xeinfo is built with your base compiler. I'd try with an older
or more recent base GNAT version. It's more likely a latent bug in
GCC 4.3.1 only showing now because xeinfo dependencies have changed.

> > chatr xeinfo
> 
> This is debian linux.  I will try debug xeinfo when the current build
> completes.

Ooops, what about "ldd xeinfo" then ?

Arno


-- 


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

Re: [Bug ada/37034] /bin/sh: line 1: 26087 Aborted (core dumped) ./xsinfo ../../sinfo.h

[Arnaud Charlet]

> > > mkdir -p ada/bldtools/einfo
> > > (cd ada/bldtools/sinfo && gnatmake -q xsinfo && ./xsinfo ../../sinfo.h )
> > > rm -f ada/bldtools/einfo/einfo.ads ada/bldtools/einfo/einfo.adb
> > > ada/bldtools/einfo/xeinfo.adb
> > > cp -p ../../gcc/gcc/ada/einfo.ads ../../gcc/gcc/ada/einfo.adb
> > > ../../gcc/gcc/ada/xeinfo.adb ada/bldtools/einfo
> > > (cd ada/bldtools/einfo && gnatmake -q xeinfo && ./xeinfo ../../einfo.h )
> > > /bin/sh: line 1: 26087 Aborted (core dumped) ./xsinfo
> > 
> > Sounds like your base Ada compiler may be corrupted, since the line above
> > calls 'gnatmake', it does not use the newly built compiler.
> 
> I belive it is xeinfo that's dropping core.  This occurs in stage2.

Right, and xeinfo is built with your base compiler. I'd try with an older
or more recent base GNAT version. It's more likely a latent bug in
GCC 4.3.1 only showing now because xeinfo dependencies have changed.

> > chatr xeinfo
> 
> This is debian linux.  I will try debug xeinfo when the current build
> completes.

Ooops, what about "ldd xeinfo" then ?

Arno

[Bug c/37044] Heisenbug: SVN of gcc throws internal compiler error on PPC

[pinskia at gmail dot com]

--- Comment #2 from pinskia at gmail dot com  2008-08-07 05:48 ---
Subject: Re:  Heisenbug: SVN of gcc throws internal compiler error on PPC



Sent from my iPhone

On Aug 6, 2008, at 22:30, "contact at multimedia dot cx"
<[EMAIL PROTECTED] 
 > wrote:

>
>
> --- Comment #1 from contact at multimedia dot cx  2008-08-07  
> 05:30 ---
> The same thing happens with gcc SVN-138833 (along with FFmpeg SVN  
> 14654)--
> dca.c file compilation crashes but not with -save-temps.
>

Please attach the preprocessed source.  This is most likely a GC issue.

-- Pinski



>
> -- 
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37044
>


-- 


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

Re: [Bug c/37044] Heisenbug: SVN of gcc throws internal compiler error on PPC

[Andrew Thomas Pinski]

Sent from my iPhone

On Aug 6, 2008, at 22:30, "contact at multimedia dot cx" <[EMAIL PROTECTED] 
> wrote:





--- Comment #1 from contact at multimedia dot cx  2008-08-07  
05:30 ---
The same thing happens with gcc SVN-138833 (along with FFmpeg SVN  
14654)--

dca.c file compilation crashes but not with -save-temps.



Please attach the preprocessed source.  This is most likely a GC issue.

-- Pinski





--


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

[Bug c++/12242] g++ should warn about out-of-range int->enum conversions

[bangerth at dealii dot org]

--- Comment #15 from bangerth at dealii dot org  2008-08-07 05:41 ---
Hi Manu,
just saw your patch for PR 12242 and have a comment: I believe the warning
message would be much better if it said *why* the result is unspecified (if the
expression being cast is a bit more complicated then it may not be immediately
clear to the casual observer that the reason is that the value is out of range;
one could also think that for whatever reason conversions between enums are
unspecified -- which of course isn't the true reason).

So I think a better wording would be
+   warning (OPT_Wconversion, 
+"the result of %(%E)%> is unspecified because
the " 
+   "value is out of range for type %T",
+type, expr, type);

Best
  Wolfgang


-- 

bangerth at dealii dot org changed:

   What|Removed |Added

 CC||bangerth at dealii dot org


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

[Bug c++/12242] g++ should warn about out-of-range int->enum conversions

[bangerth at dealii dot org]

--- Comment #14 from bangerth at dealii dot org  2008-08-07 05:41 ---
Patch now here:
  http://gcc.gnu.org/ml/gcc-patches/2008-08/msg00436.html


-- 


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

[Bug c/37044] Heisenbug: SVN of gcc throws internal compiler error on PPC

[contact at multimedia dot cx]

--- Comment #1 from contact at multimedia dot cx  2008-08-07 05:30 ---
The same thing happens with gcc SVN-138833 (along with FFmpeg SVN 14654)--
dca.c file compilation crashes but not with -save-temps.


-- 


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

[Bug middle-end/29256] [4.2/4.3/4.4 regression] loop performance regression

[bonzini at gnu dot org]

--- Comment #28 from bonzini at gnu dot org  2008-08-07 05:01 ---
fwprop seems the right place to do that indeed.

Only thing, I wonder you need to "find a location to add the constant": it
could be enough to do

  *x = simplify_gen_binary (PLUS, Pmode, *x, cst_to_add);

because simplify_plus_minus should have machinery to do what you are doing
already.  Indeed I wonder if this code shouldn't go in simplify_plus_minus so
that propagate_rtx would call it automatically.

Also when you compute cst_to_add you can use the _const_ version of the
simplification routine.


-- 


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

[Bug c/37044] New: Heisenbug: SVN of gcc throws internal compiler error on PPC

[contact at multimedia dot cx]

For several months, I have been keeping abreast of recent gcc-SVN builds on
several platforms for automatically building and testing a certain free
software project. The build for PowerPC has intermittently given internal
compiler errors. It has been difficult to nail down because the internal error
might go away depending on the state of the project source tree being compiled.

I usually rebuild the gcc-SVN copies once every 1-3 weeks. The gcc build
process follows this pattern:

'svn update' in my local copy of the gcc tree
'mkdir build-gcc' in an unrelated directory
'/path/to/gcc-svn/configure --enable-languages=c
--prefix=/usr/local/gcc-138544-20080801' -- this reflects the last build I
made: SVN revision 138544, built on 2008-08-01

So I build and install the C compiler. When I compile the program in question
(ffmpeg) and the build fails, it happens on one of a few files. With the build
mentioned above, this command fails:

 /usr/local/gcc-138544-20080801/bin/gcc -DHAVE_AV_CONFIG_H
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_ISOC9X_SOURCE -I.
-I"/home/melanson/ffmpeg/ffmpeg-main" -fomit-frame-pointer -maltivec
-mabi=altivec -Wdeclaration-after-statement -Wall -Wno-switch
-Wdisabled-optimization -Wpointer-arith -Wredundant-decls -Wno-pointer-sign
-Wcast-qual -Wwrite-strings -Wtype-limits -O3 -fno-math-errno -fno-signed-zeros
   -fPIC -DPIC -c -o libavcodec/dca.o
/home/melanson/ffmpeg/ffmpeg-main/libavcodec/dca.c

This is the error:

/home/melanson/ffmpeg/ffmpeg-main/libavcodec/dca.c: In function
'dca_subsubframe':
/home/melanson/ffmpeg/ffmpeg-main/libavcodec/dca.c:941: warning: array
subscript is above array bounds
/home/melanson/ffmpeg/ffmpeg-main/libavcodec/dca.c:941: warning: array
subscript is above array bounds
/home/melanson/ffmpeg/ffmpeg-main/libavcodec/dca.c:941: warning: array
subscript is above array bounds
/home/melanson/ffmpeg/ffmpeg-main/libavcodec/dca.c: In function
'dca_decode_frame':
/home/melanson/ffmpeg/ffmpeg-main/libavcodec/dca.c:1200: internal compiler
error: in tree_node_structure, at tree.c:2412
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.

Now here's the Heisenbug unpredictability: I added -save-temps as requested on
the bug page. The compiler does not crash.

I'm working on a new PPC compiler build right now. I just wanted to finally
enter this bug as a placeholder. I hope to have more data soon.


-- 
   Summary: Heisenbug: SVN of gcc throws internal compiler error on
PPC
   Product: gcc
   Version: 4.4.0
Status: UNCONFIRMED
  Severity: major
  Priority: P3
 Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: contact at multimedia dot cx
 GCC build triplet: powerpc-unknown-linux-gnu
  GCC host triplet: powerpc-unknown-linux-gnu
GCC target triplet: powerpc-unknown-linux-gnu


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

[Bug libgomp/33720] A negative value in OpenMP clause num_threads is not detected at runtime

[manu at gcc dot gnu dot org]

--- Comment #3 from manu at gcc dot gnu dot org  2008-08-07 02:55 ---
(In reply to comment #2)
> I'm not sure we should do anything about this.
> We have a warning if the compiler can detect non-positive value at compile
> time,
> but we certainly can't ever issue any diagnostic at runtime for num_threads
> 0 (because the implementation uses that value to mean no num_threads clause 
> was
> present) and I'm not convinced the runtime library needs to be verbose to
> stderr.  So e.g. silently assuming just one thread is IMHO better than doing
> gomp_fatal in there.  You shouldn't expect any particular behavior from 
> program
> which triggers undefined behavior.

But in this case the value is negative, not zero, and it seems that gomp_fatal
is already being called:

libgomp: Out of memory allocating 34359738400 bytes

It will be better to print the cause of that "out of memory" error, that is,
that the number of threads was negative.


-- 

manu at gcc dot gnu dot org changed:

   What|Removed |Added

 CC||manu at gcc dot gnu dot org,
   ||jakub at gcc dot gnu dot org


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

[Bug c++/35158] g++ does not compile valid C++ for loops with -fopenmp

[manu at gcc dot gnu dot org]

--- Comment #3 from manu at gcc dot gnu dot org  2008-08-06 22:26 ---
CC Jakub,

Is this initialization allowed in OpenMP or not? I have a patch that handles
it, so we can either allow it or we can give an error such:

error: parenthesized initialization not allowed in OpenMP ‘for’


-- 

manu at gcc dot gnu dot org changed:

   What|Removed |Added

 CC||jakub at gcc dot gnu dot org


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

[Bug c++/37043] fails to find operator match when constructing object on the fly

[pinskia at gcc dot gnu dot org]

--- Comment #1 from pinskia at gcc dot gnu dot org  2008-08-06 22:13 ---
You cannot bind a rvalue to a reference, only a constant reference or to a non
reference.


-- 


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

[Bug c++/37043] New: fails to find operator match when constructing object on the fly

[scott at stg dot net]

Code below fails with "no match for operator>>", although works in msvc.  If
I'm doing something wrong or there is simple workaround please let me know. 
[EMAIL PROTECTED]

#include 

class FooBar
{
public:
FooBar(const char *s)
{
printf("Constructed: %s\n",s);
}
void Accept(const char *s)
{
printf("Passed: %s\n",s);
}
};

FooBar& operator>> (const char *s,FooBar& dest)
{
dest.Accept(s);
return(dest);
}

int main(int argc,char **argv)
{
FooBar test1("one");

"A">>test1;

"B">>FooBar("two");
}


-- 
   Summary: fails to find operator match when constructing object on
the fly
   Product: gcc
   Version: 4.1.2
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: scott at stg dot net


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

[Bug middle-end/29256] [4.2/4.3/4.4 regression] loop performance regression

[rakdver at gcc dot gnu dot org]

--- Comment #27 from rakdver at gcc dot gnu dot org  2008-08-06 21:56 
---
(In reply to comment #26)
> Created an attachment (id=16036)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16036&action=view) [edit]
> possible fix
> 
> One place where this can be fixed is fwprop (something like the attached
> patch).  I am not sure whether it is the right place, though; maybe cse should
> be handling this?

Also, I only checked the problem on x86; most likely, something different is
happening on ppc.


-- 


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

[Bug middle-end/29256] [4.2/4.3/4.4 regression] loop performance regression

[rakdver at gcc dot gnu dot org]

-- 

rakdver at gcc dot gnu dot org changed:

   What|Removed |Added

 CC||bonzini at gnu dot org
 AssignedTo|rakdver at gcc dot gnu dot  |unassigned at gcc dot gnu
   |org |dot org
 Status|ASSIGNED|NEW


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

[Bug middle-end/29256] [4.2/4.3/4.4 regression] loop performance regression

[rakdver at gcc dot gnu dot org]

--- Comment #26 from rakdver at gcc dot gnu dot org  2008-08-06 21:51 
---
Created an attachment (id=16036)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16036&action=view)
possible fix

One place where this can be fixed is fwprop (something like the attached
patch).  I am not sure whether it is the right place, though; maybe cse should
be handling this?


-- 


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

[Bug c/37042] New: Strict-aliasing warnings are printed for _mm_load_si128, even though __m128i is __attribute__((__may_alias__)).

[lennox at cs dot columbia dot edu]

The Intel SSE intrinsic function _mm_load_si128 prints a warning when the data
being loaded from is actually an array of int16_t, even though its argument
(__m128i*) is declared with __attribute__((__may_alias__)).

$ cat alias-warn-emmintrin.c
#include 
#include 

static const int16_t __attribute__((__aligned__(16))) tbl[8] =
{ 1, 2, 3, 4, 5, 6, 7, 8};


__m128i get_vec(void)
{
__m128i ret;

ret = _mm_load_si128((__m128i *)tbl);

return ret;
}

$ ~/GCC/bin/gcc-4.3 -O2 -Wall -msse2 -c alias-warn-emmintrin.c
alias-warn-emmintrin.c: In function ‘get_vec’:
alias-warn-emmintrin.c:12: warning: likely type-punning may break
strict-aliasing rules: object ‘*{unknown}’ of main type ‘long long int
__vector__’ is referenced at or around
/mnt/int_drive/jonathan/GCC/bin/../lib/gcc/i686-pc-linux-gnu/4.3.2/include/emmintrin.h:681
and may be aliased to object ‘tbl’ of main type ‘short int’ which is referenced
at or around alias-warn-emmintrin.c:12.

$ ~/GCC/bin/gcc-4.3 -v -O2 -Wall -msse2 -c alias-warn-emmintrin.c
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../gcc-4.3-20080731/configure --enable-threads=posix
--prefix=/home/jonathan/GCC --with-local-prefix=/usr/local
--enable-languages=c,c++,objc,fortran,obj-c++,java --enable-checking=release
--enable-ssp --disable-libssp --disable-libgcj --with-system-zlib
--enable-shared --enable-__cxa_atexit --enable-libstdcxx-allocator=new
--disable-libstdcxx-pch --program-suffix=-4.3
--enable-version-specific-runtime-libs --without-system-libunwind
--with-cpu=generic
Thread model: posix
gcc version 4.3.2 20080731 (prerelease) (GCC)
COLLECT_GCC_OPTIONS='-v' '-O2' '-Wall' '-msse2' '-c' '-mtune=generic'
 /mnt/int_drive/jonathan/GCC/bin/../libexec/gcc/i686-pc-linux-gnu/4.3.2/cc1
-quiet -v -iprefix
/mnt/int_drive/jonathan/GCC/bin/../lib/gcc/i686-pc-linux-gnu/4.3.2/
alias-warn-emmintrin.c -quiet -dumpbase alias-warn-emmintrin.c -msse2
-mtune=generic -auxbase alias-warn-emmintrin -O2 -Wall -version -o
/tmp/ccKGNLjp.s
ignoring nonexistent directory
"/mnt/int_drive/jonathan/GCC/bin/../lib/gcc/i686-pc-linux-gnu/4.3.2/../../../../i686-pc-linux-gnu/include"
ignoring duplicate directory
"/mnt/int_drive/jonathan/GCC/bin/../lib/gcc/../../lib/gcc/i686-pc-linux-gnu/4.3.2/include"
ignoring duplicate directory
"/mnt/int_drive/jonathan/GCC/bin/../lib/gcc/../../lib/gcc/i686-pc-linux-gnu/4.3.2/include-fixed"
ignoring nonexistent directory
"/mnt/int_drive/jonathan/GCC/bin/../lib/gcc/../../lib/gcc/i686-pc-linux-gnu/4.3.2/../../../../i686-pc-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
 /mnt/int_drive/jonathan/GCC/bin/../lib/gcc/i686-pc-linux-gnu/4.3.2/include

/mnt/int_drive/jonathan/GCC/bin/../lib/gcc/i686-pc-linux-gnu/4.3.2/include-fixed
 /usr/local/include
 /mnt/int_drive/jonathan/GCC/bin/../lib/gcc/../../include
 /usr/include
End of search list.
GNU C (GCC) version 4.3.2 20080731 (prerelease) (i686-pc-linux-gnu)
compiled by GNU C version 4.3.2 20080731 (prerelease), GMP version
4.2.1, MPFR version 2.2.1.
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
Compiler executable checksum: 3f9a15ebf1f37358d0142d31f7849434
alias-warn-emmintrin.c: In function ‘get_vec’:
alias-warn-emmintrin.c:12: warning: likely type-punning may break
strict-aliasing rules: object ‘*{unknown}’ of main type ‘long long int
__vector__’ is referenced at or around
/mnt/int_drive/jonathan/GCC/bin/../lib/gcc/i686-pc-linux-gnu/4.3.2/include/emmintrin.h:681
and may be aliased to object ‘tbl’ of main type ‘short int’ which is referenced
at or around alias-warn-emmintrin.c:12.
COLLECT_GCC_OPTIONS='-v' '-O2' '-Wall' '-msse2' '-c' '-mtune=generic'
 as -V -Qy -o alias-warn-emmintrin.o /tmp/ccKGNLjp.s
GNU assembler version 2.17.50 (i586-suse-linux) using BFD version (GNU
Binutils) 2.17.50.20070726-14 (SUSE Linux)
COMPILER_PATH=/mnt/int_drive/jonathan/GCC/bin/../libexec/gcc/i686-pc-linux-gnu/4.3.2/:/mnt/int_drive/jonathan/GCC/bin/../libexec/gcc/
LIBRARY_PATH=/mnt/int_drive/jonathan/GCC/bin/../lib/gcc/i686-pc-linux-gnu/4.3.2/:/mnt/int_drive/jonathan/GCC/bin/../lib/gcc/:/mnt/int_drive/jonathan/GCC/bin/../lib/gcc/i686-pc-linux-gnu/4.3.2/../../../:/lib/:/usr/lib/
COLLECT_GCC_OPTIONS='-v' '-O2' '-Wall' '-msse2' '-c' '-mtune=generic'


-- 
   Summary: Strict-aliasing warnings are printed for _mm_load_si128,
even though __m128i is __attribute__((__may_alias__)).
   Product: gcc
   Version: 4.3.2
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: lennox at cs dot columbia dot edu
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


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

[Bug middle-end/35432] [4.2/4.3/4.4 regression] ICE with zero-sized array

[rguenth at gcc dot gnu dot org]

--- Comment #7 from rguenth at gcc dot gnu dot org  2008-08-06 21:04 ---
Subject: Bug 35432

Author: rguenth
Date: Wed Aug  6 21:03:07 2008
New Revision: 138828

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=138828
Log:
2008-08-06  Richard Guenther  <[EMAIL PROTECTED]>

PR middle-end/35432
* gcc.c-torture/compile/pr35432.c: Remove duplicate.

Modified:
branches/gcc-4_3-branch/gcc/testsuite/ChangeLog
branches/gcc-4_3-branch/gcc/testsuite/gcc.c-torture/compile/pr35432.c


-- 


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

[Bug c/37041] New: -Wc++-compat refinements

[jsm28 at gcc dot gnu dot org]

-Wc++-compat should allow bool, wchar_t, char16_t and char32_t as typedefs
defined in system headers, while warning if they are used other than as types
or the typedefs are defined other than in system headers.

-Wc++-compat should warn for asm and inline when used in a C mode where they
are identifiers not keywords, but not in a mode when they are keywords and
not for the __ variants in any case.

-Wc++-compat should warn for uses of the alternative representations for
operators and punctuators such as "and", including uses as macro names (except
when defined in system headers, because of iso646.h) and macro parameter names.


-- 
   Summary: -Wc++-compat refinements
   Product: gcc
   Version: 4.4.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jsm28 at gcc dot gnu dot org


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

[Bug middle-end/36450] [4.4 Regression] ICE in insert_restore/insert_save with GET_MODE_ALIGNMENT mem

[hjl dot tools at gmail dot com]

--- Comment #16 from hjl dot tools at gmail dot com  2008-08-06 20:50 
---
Should be fixed now.


-- 

hjl dot tools at gmail dot com changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED


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

[Bug middle-end/36450] [4.4 Regression] ICE in insert_restore/insert_save with GET_MODE_ALIGNMENT mem

[vmakarov at gcc dot gnu dot org]

--- Comment #15 from vmakarov at gcc dot gnu dot org  2008-08-06 20:46 
---
Subject: Bug 36450

Author: vmakarov
Date: Wed Aug  6 20:44:53 2008
New Revision: 138826

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=138826
Log:
2008-08-04  H.J. Lu  <[EMAIL PROTECTED]>

PR middle-end/36450
* caller-save.c (insert_restore): Replace
PREFERRED_STACK_BOUNDARY with MAX_SUPPORTED_STACK_ALIGNMENT.
(insert_save): Likewise.


Modified:
branches/ira/gcc/ChangeLog
branches/ira/gcc/caller-save.c


-- 


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

[Bug debug/37022] [4.4 regression] internal compiler error: in compute_barrier_args_size

[andreast at gcc dot gnu dot org]

-- 

andreast at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever Confirmed|0   |1
   Last reconfirmed|-00-00 00:00:00 |2008-08-06 20:29:34
   date||


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

[Bug target/33548] Core dump on HPUX

[sje at cup dot hp dot com]

--- Comment #2 from sje at cup dot hp dot com  2008-08-06 20:28 ---
I am resolving this as invalid since it is not a GCC bug (unless you consider
not using -Z to be a bug).  There is a patch for libpam which should fix the
null pointer reference available from HP.  It is HP patch PHCO_37076.


-- 

sje at cup dot hp dot com changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution||INVALID


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

[Bug target/36806] [4.4 Regression] I/Os hang at rev. 137631 on darwin9

[andreast at gcc dot gnu dot org]

--- Comment #25 from andreast at gcc dot gnu dot org  2008-08-06 20:25 
---
I'd say it is not an issue anymore. I close this bug now. On different opinions
please reopen.


-- 

andreast at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED


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

[Bug bootstrap/36918] [4.4 regression] Bootstrap failure on sparc: assertion failure in options.c

[andreast at gcc dot gnu dot org]

--- Comment #9 from andreast at gcc dot gnu dot org  2008-08-06 20:23 
---
Fixed. Should set the state too 


-- 

andreast at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution||FIXED


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

[Bug bootstrap/36918] [4.4 regression] Bootstrap failure on sparc: assertion failure in options.c

[andreast at gcc dot gnu dot org]

--- Comment #8 from andreast at gcc dot gnu dot org  2008-08-06 20:22 
---
Fixed.


-- 


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

[Bug c++/35158] g++ does not compile valid C++ for loops with -fopenmp

[manu at gcc dot gnu dot org]

--- Comment #2 from manu at gcc dot gnu dot org  2008-08-06 20:14 ---
Reconfirmed in GCC 4.4


-- 

manu at gcc dot gnu dot org changed:

   What|Removed |Added

  Known to fail||4.4.0 4.3.0
   Last reconfirmed|2008-02-13 22:10:56 |2008-08-06 20:14:08
   date||


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

[Bug ada/37040] GNAT Socket Code Broken on RTEMS

[joel at gcc dot gnu dot org]

--- Comment #1 from joel at gcc dot gnu dot org  2008-08-06 20:01 ---
Created an attachment (id=16035)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16035&action=view)
Updates Ada socket code to compile

2008-05-28  Joel Sherrill <[EMAIL PROTECTED]>

* gen-soccon-rtems.ads: Regenerated.
* gsocket.h, gen-soccon.c, socket.c: Make new additions support RTEMS.


-- 


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

[Bug ada/37040] New: GNAT Socket Code Broken on RTEMS

[joel at gcc dot gnu dot org]

Does not compile.  Requires attached patch.


-- 
   Summary: GNAT Socket Code Broken on RTEMS
   Product: gcc
   Version: 4.4.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: ada
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: joel at gcc dot gnu dot org
GCC target triplet: *-rtems*


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

[Bug ada/35576] Ada HW Interrupt Task Enhancement

[joel at gcc dot gnu dot org]

--- Comment #18 from joel at gcc dot gnu dot org  2008-08-06 19:47 ---
Created an attachment (id=16034)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16034&action=view)
Latest version against revision 138553

Goes with http://gcc.gnu.org/bugzilla/attachment.cgi?id=16033

s-interr-hwint.adb can be diffed against s-interr-vxworks.adb to see what was
done to make it generic.


-- 

joel at gcc dot gnu dot org changed:

   What|Removed |Added

  Attachment #16032|0   |1
is obsolete||


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

[Bug ada/35576] Ada HW Interrupt Task Enhancement

[joel at gcc dot gnu dot org]

--- Comment #17 from joel at gcc dot gnu dot org  2008-08-06 19:40 ---
Created an attachment (id=16033)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16033&action=view)
New file not in 20080806 diff.

Must go with http://gcc.gnu.org/bugzilla/attachment.cgi?id=16032


-- 


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

[Bug ada/35576] Ada HW Interrupt Task Enhancement

[joel at gcc dot gnu dot org]

--- Comment #16 from joel at gcc dot gnu dot org  2008-08-06 19:38 ---
(From update of attachment 15724)
Obsoleted by 20080806 patch


-- 

joel at gcc dot gnu dot org changed:

   What|Removed |Added

  Attachment #15724|0   |1
is obsolete||


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

[Bug ada/35576] Ada HW Interrupt Task Enhancement

[joel at gcc dot gnu dot org]

--- Comment #15 from joel at gcc dot gnu dot org  2008-08-06 19:37 ---
Created an attachment (id=16032)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16032&action=view)
Lastest version of patch (against rev 138553)

hwint tested on sparc. ACATS results posted for sparc, mips, i386, powerpc, and
arm


-- 


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

[Bug ada/35298] GNAT Bug Box

[joel at gcc dot gnu dot org]

--- Comment #2 from joel at gcc dot gnu dot org  2008-08-06 19:35 ---
*** Bug 36940 has been marked as a duplicate of this bug. ***


-- 


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

[Bug ada/36940] Compiler error on many ACATS tests on bfin target

[joel at gcc dot gnu dot org]

--- Comment #1 from joel at gcc dot gnu dot org  2008-08-06 19:35 ---


*** This bug has been marked as a duplicate of 35298 ***


-- 

joel at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution||DUPLICATE


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

[Bug ada/36937] Compiler error on ACATS cxg1004

[joel at gcc dot gnu dot org]

--- Comment #4 from joel at gcc dot gnu dot org  2008-08-06 19:34 ---
Does not happen in my most recent test.

arm-rtems4.9-gcc (GCC) 4.4.0 20080802 (experimental) [trunk revision 138553]


-- 

joel at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution||FIXED


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

[Bug fortran/37039] New: Cray pointer with pointee DIMENSION statement after POINTER statement

[burnus at gcc dot gnu dot org]

From
http://groups.google.com/group/comp.lang.fortran/browse_thread/thread/14ce82ff2838fb9a

I think it is a valid program - at least in the sense that other
Cray-pointer-supporting programs support it.

The following program is rejected with

 tab(n) = 0
  1
Error: Unexpected STATEMENT FUNCTION statement at (1)

It works if one swaps the "INTEGER, dimension(1:nnode) :: tab" with the
"POINTER(ip_tab,tab)" line.

  subroutine test(nnode)
  implicit none
  integer n,nnode
  pointer(ip_tab, tab)
  integer , dimension(1:nnode) :: tab
  do n=1,nnode
 tab(n) = 0
  enddo
  end subroutine test


-- 
   Summary: Cray pointer with pointee DIMENSION statement after
POINTER statement
   Product: gcc
   Version: 4.4.0
Status: UNCONFIRMED
  Keywords: rejects-valid
  Severity: normal
  Priority: P3
 Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: burnus at gcc dot gnu dot org


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

[Bug c++/36460] No space between >'s not always handled in C++0x

[dgregor at gcc dot gnu dot org]

--- Comment #7 from dgregor at gcc dot gnu dot org  2008-08-06 19:12 ---
Fixed on the trunk.


-- 

dgregor at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution||FIXED
   Target Milestone|--- |4.4.0


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

[Bug c++/36460] No space between >'s not always handled in C++0x

[dgregor at gcc dot gnu dot org]

--- Comment #6 from dgregor at gcc dot gnu dot org  2008-08-06 19:09 ---
Subject: Bug 36460

Author: dgregor
Date: Wed Aug  6 19:08:12 2008
New Revision: 138819

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=138819
Log:
2008-08-06  Douglas Gregor  <[EMAIL PROTECTED]>

   PR c++/36460
   * parser.c (cp_parser_template_argument): Don't assume that '>>'
   following a type-id is an error when in C++0x mode.

2008-08-06  Douglas Gregor  <[EMAIL PROTECTED]>

   PR c++/36460
   * g++.dg/cpp0x/bracket3.C: Add another test case for the >>
   warning under -Wc++0x-compat.
   * g++.dg/cpp0x/bracket4.C: Add testcase for PR c++/36460.


Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/parser.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/g++.dg/cpp0x/bracket3.C
trunk/gcc/testsuite/g++.dg/cpp0x/bracket4.C


-- 


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

[Bug c++/20475] static_cast falsely allows const to be cast away

[manu at gcc dot gnu dot org]

--- Comment #12 from manu at gcc dot gnu dot org  2008-08-06 18:42 ---
This always produces a warning by default now. Thus FIXED.


-- 

manu at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED
   Target Milestone|--- |4.4.0


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

[Bug driver/30330] -Wdeprecated is not documented

[manu at gcc dot gnu dot org]

--- Comment #6 from manu at gcc dot gnu dot org  2008-08-06 18:36 ---
This is FIXED in GCC 4.4


-- 

manu at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED
   Target Milestone|--- |4.4.0


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

[Bug c/20410] Add support for UTF-16 string syntax to C and C++

[paolo dot carlini at oracle dot com]

--- Comment #5 from paolo dot carlini at oracle dot com  2008-08-06 17:19 
---
That patch is in (+ some follow ups, see also C++/33979 for updated
references). As been applied to mainline, thus the new features will be
available in gcc4.4.0.


-- 


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

[Bug c/20410] Add support for UTF-16 string syntax to C and C++

[grhoten at jtcsv dot com]

--- Comment #4 from grhoten at jtcsv dot com  2008-08-06 17:07 ---
Has this recently been implemented? If so, which version will it be available?

I recently noticed this patch mentioned for inclusion.
http://gcc.gnu.org/ml/gcc-patches/2008-04/msg01235.html


-- 


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

[Bug ada/37038] Bogus warning from GCC

[sam at gcc dot gnu dot org]

--- Comment #4 from sam at gcc dot gnu dot org  2008-08-06 16:57 ---
Andrew, you're right, I got confused by the build_binary_op() which is present
both in ada/gcc-interface/utils2.c and c-typeck.c, and that the warning appears
as is in c-common.c.

The warning is likely to come from tree-vrp.c.


-- 


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

[Bug c++/26785] "extra qualification" error gives line number of end of declaration

[manu at gcc dot gnu dot org]

--- Comment #5 from manu at gcc dot gnu dot org  2008-08-06 16:42 ---
Fixed in GCC 4.4.


-- 

manu at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED
   Target Milestone|--- |4.4.0


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

[Bug bootstrap/37000] gen-classlist.sh uses unrecognized 'test' arguments

[deisner at gmail dot com]

--- Comment #3 from deisner at gmail dot com  2008-08-06 16:41 ---
My bug appears to be a duplicate bug, anyway:

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



*** This bug has been marked as a duplicate of 25557 ***


-- 

deisner at gmail dot com changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution||DUPLICATE


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

[Bug c++/26785] "extra qualification" error gives line number of end of declaration

[manu at gcc dot gnu dot org]

--- Comment #4 from manu at gcc dot gnu dot org  2008-08-06 16:38 ---
Subject: Bug 26785

Author: manu
Date: Wed Aug  6 16:37:06 2008
New Revision: 138816

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=138816
Log:
2008-08-06  Manuel Lopez-Ibanez  <[EMAIL PROTECTED]>

PR 26785
* diagnostic.c (permerror_at): New.
* toplev.h (permerror_at): Declare.
cp/
* decl.c (grokdeclarator): Use explicit location with
permerror_at.
testsuite/
* g++.dg/warn/pr26785.C: New.

Added:
trunk/gcc/testsuite/g++.dg/warn/pr26785.C
Modified:
trunk/gcc/ChangeLog
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/decl.c
trunk/gcc/diagnostic.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/toplev.h


-- 


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

[Bug c++/8715] '~' operator for unsigned char and conversion to bool

[manu at gcc dot gnu dot org]

--- Comment #12 from manu at gcc dot gnu dot org  2008-08-06 16:33 ---
Fixed in GCC 4.4.


-- 

manu at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED
   Target Milestone|--- |4.4.0


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

[Bug c++/8715] '~' operator for unsigned char and conversion to bool

[manu at gcc dot gnu dot org]

--- Comment #11 from manu at gcc dot gnu dot org  2008-08-06 16:19 ---
Subject: Bug 8715

Author: manu
Date: Wed Aug  6 16:17:41 2008
New Revision: 138814

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=138814
Log:
2008-08-06  Manuel Lopez-Ibanez  <[EMAIL PROTECTED]>

PR 8715
* c-common.c (warn_for_sign_compare): New. Handle separately the
case that 'constant' is zero.
* c-typeck.c (build_binary_op): Move code to c-common.c
cp/
* typeck.c (cp_build_binary_op): Move code to c-common.c.
testsuite/
* gcc.dg/pr8715.c: New.
* g++.dg/warn/pr8715.C: New.

Added:
trunk/gcc/testsuite/g++.dg/warn/pr8715.C
trunk/gcc/testsuite/gcc.dg/pr8715.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/c-common.c
trunk/gcc/c-common.h
trunk/gcc/c-typeck.c
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/typeck.c
trunk/gcc/testsuite/ChangeLog


-- 


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

[Bug c++/37029] Exception from shared library's functions or methods that return float (double, long double) value cannot be caught on HP-UX.

[v dot grikyan at sam-solutions dot net]

--- Comment #5 from v dot grikyan at sam-solutions dot net  2008-08-06 
16:11 ---
Hi Dave,

thank you for your fast reply.
Have we understood correctly - you will try to reproduce this error on your HP
platform?
If yes and if it works on your side - please let us know what patches are
installed on your system.
Thanks in advance.

Valery.


-- 


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

[Bug ada/37038] Bogus warning from GCC

[pinskia at gmail dot com]

--- Comment #3 from pinskia at gmail dot com  2008-08-06 15:46 ---
Subject: Re:  Bogus warning from GCC



Sent from my iPhone

On Aug 6, 2008, at 8:39, "sam at gcc dot gnu dot org" <[EMAIL PROTECTED] 
 > wrote:

>
>
> --- Comment #2 from sam at gcc dot gnu dot org  2008-08-06 15:39  
> ---
> The warning comes from a range check which is emitted by Gigi. The  
> backend
> knows that this check is useless, and warns about it. As far as I  
> can tell,
> there is no way to suppress the warning in shorten_compare (c- 
> common.c), except
> by setting a global option (OPT_Wtype_limits) to false.

C-common.c being included by the Ada front-end That is a c front- 
end file.

-- Pinski


>
>
>
> -- 
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37038
>


-- 


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

[Bug middle-end/37010] -mno-accumulate-outgoing-args doesn't work with stack alignment

[hjl dot tools at gmail dot com]

--- Comment #19 from hjl dot tools at gmail dot com  2008-08-06 15:45 
---
Fixed.


-- 

hjl dot tools at gmail dot com changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution||FIXED


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

[Bug middle-end/37010] -mno-accumulate-outgoing-args doesn't work with stack alignment

[hjl at gcc dot gnu dot org]

--- Comment #18 from hjl at gcc dot gnu dot org  2008-08-06 15:45 ---
Subject: Bug 37010

Author: hjl
Date: Wed Aug  6 15:43:46 2008
New Revision: 138808

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=138808
Log:
gcc/

2008-08-06  H.J. Lu  <[EMAIL PROTECTED]>

PR middle-end/37010
* calls.c (expand_call): Use the biggest preferred stack
boundary.

gcc/testsuite/

2008-08-06  H.J. Lu  <[EMAIL PROTECTED]>

PR middle-end/37010
* gcc.dg/torture/stackalign/push-1.c: New.

Added:
trunk/gcc/testsuite/gcc.dg/torture/stackalign/push-1.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/calls.c
trunk/gcc/testsuite/ChangeLog


-- 


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

[Bug middle-end/37009] No need to align stack when incoming stack is aligned

[hjl dot tools at gmail dot com]

--- Comment #5 from hjl dot tools at gmail dot com  2008-08-06 15:44 ---
Fixed.


-- 

hjl dot tools at gmail dot com changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution||FIXED


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

Re: [Bug ada/37038] Bogus warning from GCC

[Andrew Thomas Pinski]

Sent from my iPhone

On Aug 6, 2008, at 8:39, "sam at gcc dot gnu dot org" <[EMAIL PROTECTED] 
> wrote:





--- Comment #2 from sam at gcc dot gnu dot org  2008-08-06 15:39  
---
The warning comes from a range check which is emitted by Gigi. The  
backend
knows that this check is useless, and warns about it. As far as I  
can tell,
there is no way to suppress the warning in shorten_compare (c- 
common.c), except

by setting a global option (OPT_Wtype_limits) to false.


C-common.c being included by the Ada front-end That is a c front- 
end file.


-- Pinski






--


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

[Bug ada/37038] Bogus warning from GCC

[sam at gcc dot gnu dot org]

--- Comment #2 from sam at gcc dot gnu dot org  2008-08-06 15:39 ---
The warning comes from a range check which is emitted by Gigi. The backend
knows that this check is useless, and warns about it. As far as I can tell,
there is no way to suppress the warning in shorten_compare (c-common.c), except
by setting a global option (OPT_Wtype_limits) to false.


-- 


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

[Bug target/36613] [4.2/4.3/4.4 Regression] likely codegen bug

[matz at gcc dot gnu dot org]

--- Comment #12 from matz at gcc dot gnu dot org  2008-08-06 15:36 ---
Subject: Bug 36613

Author: matz
Date: Wed Aug  6 15:34:45 2008
New Revision: 138807

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=138807
Log:
PR target/36613

* reload.c (push_reload): Merge in,out,in_reg,out_reg members
for reused reload, instead of overwriting them.

* gcc.target/i386/pr36613.c: New testcase.

Added:
trunk/gcc/testsuite/gcc.target/i386/pr36613.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/reload.c
trunk/gcc/testsuite/ChangeLog


-- 


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

[Bug c++/37029] Exception from shared library's functions or methods that return float (double, long double) value cannot be caught on HP-UX.

[dave at hiauly1 dot hia dot nrc dot ca]

--- Comment #4 from dave at hiauly1 dot hia dot nrc dot ca  2008-08-06 
15:35 ---
Subject: Re:  Exception from shared library's functions or methods that return
float (double, long double) value cannot be cauO

> As we understand (looking at gcc sources), sjlj-mechanism can be set only
> during building of gcc.

Correct.  The default for HP-UX 11 is dwarf2 exceptions.  However,
sjlj exceptions are forced in current versions for HP-UX 10.

> So it seems GAS version is correct but anyway the test application does not
> work...

I would also suggest applying the latest HP linker and libc patches
for your system.

I would try to confirm the bug.  The dwarf2 unwind mechanism depends
on extracting values from the context.  The floating point registers
are handled a bit differently than general registers.  The context
information is somewhat complicated as it has to handle different
PA architectures, 32 and 64-bit code, etc.

Dave


-- 


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

[Bug middle-end/37009] No need to align stack when incoming stack is aligned

[hjl at gcc dot gnu dot org]

--- Comment #4 from hjl at gcc dot gnu dot org  2008-08-06 15:30 ---
Subject: Bug 37009

Author: hjl
Date: Wed Aug  6 15:29:37 2008
New Revision: 138806

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=138806
Log:
gcc/

2008-08-06  H.J. Lu  <[EMAIL PROTECTED]>

PR middle-end/37009
* cfgexpand.c (expand_stack_alignment): Check parm_stack_boundary
for incoming stack boundary.

* function.c (assign_parm_find_entry_rtl): Update
parm_stack_boundary.

* function.h (rtl_data): Add parm_stack_boundary.

* config/i386/i386.c (ix86_finalize_stack_realign_flags): Check
parm_stack_boundary for incoming stack boundary.

gcc/testsuite/

2008-08-06  H.J. Lu  <[EMAIL PROTECTED]>

PR middle-end/37009
* gcc.dg/torture/stackalign/alloca-2.c: New.
* gcc.dg/torture/stackalign/alloca-3.c: Likewise.
* gcc.dg/torture/stackalign/alloca-4.c: Likewise.
* gcc.dg/torture/stackalign/vararg-3.c: Likewise.
* gcc.target/i386/incoming-1.c: Likewise.
* gcc.target/i386/incoming-2.c: Likewise.
* gcc.target/i386/incoming-3.c: Likewise.
* gcc.target/i386/incoming-4.c: Likewise.
* gcc.target/i386/incoming-5.c: Likewise.

Added:
trunk/gcc/testsuite/gcc.dg/torture/stackalign/alloca-2.c
trunk/gcc/testsuite/gcc.dg/torture/stackalign/alloca-3.c
trunk/gcc/testsuite/gcc.dg/torture/stackalign/alloca-4.c
trunk/gcc/testsuite/gcc.dg/torture/stackalign/vararg-3.c
trunk/gcc/testsuite/gcc.target/i386/incoming-1.c
trunk/gcc/testsuite/gcc.target/i386/incoming-2.c
trunk/gcc/testsuite/gcc.target/i386/incoming-3.c
trunk/gcc/testsuite/gcc.target/i386/incoming-4.c
trunk/gcc/testsuite/gcc.target/i386/incoming-5.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/cfgexpand.c
trunk/gcc/config/i386/i386.c
trunk/gcc/function.c
trunk/gcc/function.h
trunk/gcc/testsuite/ChangeLog


-- 


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

[Bug ada/37034] /bin/sh: line 1: 26087 Aborted (core dumped) ./xsinfo ../../sinfo.h

[dave at hiauly1 dot hia dot nrc dot ca]

--- Comment #2 from dave at hiauly1 dot hia dot nrc dot ca  2008-08-06 
15:14 ---
Subject: Re:  /bin/sh: line 1: 26087 Aborted  (core dumped) ./xsinfo
../../sinfo.h

> --- Comment #1 from charlet at adacore dot com  2008-08-06 06:39 ---
> Subject: Re:   New: /bin/sh: line 1: 26087 Aborted  (core
> dumped) ./xsinfo ../../sinfo.h
> 
> > mkdir -p ada/bldtools/einfo
> > (cd ada/bldtools/sinfo && gnatmake -q xsinfo && ./xsinfo ../../sinfo.h )
> > rm -f ada/bldtools/einfo/einfo.ads ada/bldtools/einfo/einfo.adb
> > ada/bldtools/einfo/xeinfo.adb
> > cp -p ../../gcc/gcc/ada/einfo.ads ../../gcc/gcc/ada/einfo.adb
> > ../../gcc/gcc/ada/xeinfo.adb ada/bldtools/einfo
> > (cd ada/bldtools/einfo && gnatmake -q xeinfo && ./xeinfo ../../einfo.h )
> > /bin/sh: line 1: 26087 Aborted (core dumped) ./xsinfo
> 
> Sounds like your base Ada compiler may be corrupted, since the line above
> calls 'gnatmake', it does not use the newly built compiler.

I belive it is xeinfo that's dropping core.  This occurs in stage2.
The problem was introduced after revision 138716.  It builds ok.

> Could you do:
> 
> which gnatmake

/usr/bin/gnatmake

> which gnatls

/usr/bin/gnatls

> gnatls -v

GNATLS 4.3.1
Copyright (C) 1997-2007, Free Software Foundation, Inc.

Source Search Path:
   
   /usr/lib/gcc/hppa-linux-gnu/4.3.1/adainclude/


Object Search Path:
   
   /usr/lib/gcc/hppa-linux-gnu/4.3.1/adalib/


Project Search Path:
   
   /usr/share/ada/adainclude/

> chatr xeinfo

This is debian linux.  I will try debug xeinfo when the current build
completes.


-- 


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

[Bug ada/37038] Bogus warning from GCC

[sam at gcc dot gnu dot org]

--- Comment #1 from sam at gcc dot gnu dot org  2008-08-06 14:49 ---
(read "the line containing 'Val", not "'Pos")


-- 


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

[Bug ada/37038] New: Bogus warning from GCC

[sam at gcc dot gnu dot org]

With trunk GCC, SVN revision 138798.

The following program (t.adb), when compiled with "gcc -O2", gives:

t.adb: In function ‘T’:
t.adb:6: warning: comparison always false due to limited range of data type

(probably emitted by the backend as "-gnatv" doesn't show the caret position)

Note that the warning points onto the line containing 'Pos, not the comparison
itself. And this is bogus, as if "X" contains "2#11xx#" (two high bits
set), then right shifting it by 6 positions (it is unsigned) will give "3",
which corresponds to "White".

Moreover, despites the warning, the generated code is correct and returns "0"
when the two high bits are set and "1" otherwise.

with Interfaces; use Interfaces;

function T (X : Unsigned_8) return Integer
is
   type Color is (None, Red, Blue, White);
   V : constant Color := Color'Val (Shift_Right (X, 6));
begin
   if V = White then
  return 0;
   else
  return 1;
   end if;
end T;


-- 
   Summary: Bogus warning from GCC
   Product: gcc
   Version: 4.4.0
Status: UNCONFIRMED
  Keywords: diagnostic
  Severity: normal
  Priority: P3
 Component: ada
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: sam at gcc dot gnu dot org
  GCC host triplet: i686-pc-linux-gnu


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

[Bug c++/36460] No space between >'s not always handled in C++0x

[dgregor at gcc dot gnu dot org]

--- Comment #5 from dgregor at gcc dot gnu dot org  2008-08-06 14:30 ---
Patch here: http://gcc.gnu.org/ml/gcc-patches/2008-08/msg00382.html


-- 


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

[Bug debug/37022] [4.4 regression] internal compiler error: in compute_barrier_args_size

[hjl dot tools at gmail dot com]

--- Comment #6 from hjl dot tools at gmail dot com  2008-08-06 13:51 ---
>From Xuepeng:

__attribute__((noinline, used))
void
foo (int a, ...)
{
  va_list arg;
  char *p;
  int size;

  va_start (arg, a);
  size = va_arg (arg, int);

  if (size != 2)
/*A*/ abort ();

  p = (char *) __builtin_alloca (size + 1);

  va_end (arg);

  if (v < 0)
/*B*/   abort ();  
}

This bug is caused by label optimization. Function compute_barrier_args_size
intends to walk the whole function rtl and compute args_size on BARRIERS. When
it reached the first if statement (size != 2), it will compute the destination
of this if statement, the destination was supposed to be at /*A*/ and then set
barrier_args_size[/*A*/]=cur_args_size. Unfortunately the destination /*A*/ was
optimized to /*B*/, so the actual result is barrier_args_size[/*B*/] was set to
cur_args_size. And at this point the cur_args_size was still zero, so the
barrier_args_size[/*B*/]=0. 

The __builtin_alloca will adjust stack pointer and make cur_args_size=32. 

The function compute_barrier_args_size continued and reached label /*B*/.
According to the author's comment that barrier_args_size[/*B*/] != -1 means
that the insns starting with this label have been already scanned or are in the
worklist, so the author thought barrier_args_size[/*B*/] should be
cur_args_size which is 32 now. But in fact the insns starting with this label
havn't been scanned, the barrier_args_size[/*B*/] was set to 0 just because of
label optimization. So the assert (barrier_args_size[/*B*/]== cur_args_size)
was generated.

If change label /*A*/ to something like v=0 rather than abort (), there will be
no compiler errors.


-- 


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

[Bug middle-end/36990] ICE when gcc (4.4.0-20080731) uses -fipa-cp with -O

[tsarkov at cs dot man dot ac dot uk]

--- Comment #1 from tsarkov at cs dot man dot ac dot uk  2008-08-06 13:49 
---
I saw the same problem in C++ with a simple program

#include 

void f ( std::ostream& o ) { o << std::endl; }

This happens both on i686-pc-linux-gnu and i386-apple-darwin9.4.0.


-- 

tsarkov at cs dot man dot ac dot uk changed:

   What|Removed |Added

 CC||tsarkov at cs dot man dot ac
   ||dot uk


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

[Bug c++/36460] No space between >'s not always handled in C++0x

[dgregor at gcc dot gnu dot org]

-- 

dgregor at gcc dot gnu dot org changed:

   What|Removed |Added

 AssignedTo|unassigned at gcc dot gnu   |dgregor at gcc dot gnu dot
   |dot org |org
 Status|UNCONFIRMED |ASSIGNED
 Ever Confirmed|0   |1
   Last reconfirmed|-00-00 00:00:00 |2008-08-06 13:48:53
   date||


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

[Bug c++/37037] ICE on template class member function definition after explciit template class instantation

[zweije at xs4all dot nl]

--- Comment #1 from zweije at xs4all dot nl  2008-08-06 13:48 ---
$g++ -o crash.o crash.cpp
+ /usr/bin/g++-4.3 -L/home/vincent/lib32 -o crash.o crash.cpp
crash.cpp: In static member function ‘static void S::f() [with T = int]’:
crash.cpp:6:   instantiated from here
crash.cpp:4: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.
$g++ -v
+ /usr/bin/g++-4.3 -L/home/vincent/lib32 -v
Using built-in specs.
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.3.1-2'
--with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs
--enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared
--with-system-zlib --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3
--program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug
--enable-objc-gc --enable-mpfr --enable-cld --enable-checking=release
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 4.3.1 (Debian 4.3.1-2) 
$


-- 

zweije at xs4all dot nl changed:

   What|Removed |Added

   Keywords||ice-on-invalid-code


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

[Bug c++/37037] New: ICE on template class member function definition after explciit template class instantation

[zweije at xs4all dot nl]

Following snippet causes compiler to produce internal compiler error:

typedef void F(void);
template  struct S 
{
static F f;
};
template class S;
template  void S::f(void)
{}

I'm not sure it is valid to define S::f() after instantiating the class, but
even if not, an ICE is not a proper response for a compiler in any case. #24511
mentions that all member templates (template members?) must be defined before
explicit instantiation although I don't read that per se in my copy of the
standard.

There might be a vague relation to #24791 if there is g++-internal confusion
about f being a static data member. This confusion might be exhibited in #33972
as well.

Ciao.
Vincent.


-- 
   Summary: ICE on template class member function definition after
explciit template class instantation
   Product: gcc
   Version: 4.3.1
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: zweije at xs4all dot nl
 GCC build triplet: x86_64-linux-gnu
  GCC host triplet: x86_64-linux-gnu
GCC target triplet: x86_64-linux-gnu


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

[Bug debug/37022] [4.4 regression] internal compiler error: in compute_barrier_args_size

[hjl dot tools at gmail dot com]

--- Comment #5 from hjl dot tools at gmail dot com  2008-08-06 13:32 ---
(In reply to comment #3)
> Created an attachment (id=16031)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16031&action=view) [edit]
> A smaller case.
> 
> [EMAIL PROTECTED] stackalign]$ /home/xguo2/app/stack-internal/bin/g++ -m32 
> -Os 
> -fasynchronous-unwind-tables -mpreferred-stack-boundary=4 a1.C
> a1.C: In function ‘void foo(int, ...)’:
> a1.C:27: internal compiler error: in compute_barrier_args_size, at
> dwarf2out.c:1289
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See  for instructions.

It also fails at C:

bash-3.2$ ./xgcc -B./ /tmp/a1.c -m32 -S -Os  -fasynchronous-unwind-tables
/tmp/a1.c: In function ‘foo’:
/tmp/a1.c:27: internal compiler error: in compute_barrier_args_size, at
dwarf2out.c:1319
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.


-- 


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

[Bug debug/37022] [4.4 regression] internal compiler error: in compute_barrier_args_size

[hjl dot tools at gmail dot com]

--- Comment #4 from hjl dot tools at gmail dot com  2008-08-06 13:30 ---
The new testcase

http://gcc.gnu.org/bugzilla/attachment.cgi?id=16031&action=view

also fails on Linux/ia32 and revision 138427 is the cause.


-- 

hjl dot tools at gmail dot com changed:

   What|Removed |Added

 CC||hjl dot tools at gmail dot
   ||com, Joey dot ye at intel
   ||dot com, xuepeng dot guo at
   ||intel dot com
  GCC build triplet|x86_64-apple-darwin9|
   GCC host triplet|x86_64-apple-darwin9|
 GCC target triplet|x86_64-apple-darwin9|
Summary|libffi test suite failures  |[4.4 regression] internal
   ||compiler error: in
   ||compute_barrier_args_size


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

[Bug c++/36460] No space between >'s not always handled in C++0x

[paolo dot carlini at oracle dot com]

--- Comment #4 from paolo dot carlini at oracle dot com  2008-08-06 12:22 
---
Let's ask Doug...

(by the way, Doug very kindly contributed these C++0x bits on a voluntary
basis. As a matter of courtesy, I would suggest avoiding words like "at least".
Thanks.) 


-- 

paolo dot carlini at oracle dot com changed:

   What|Removed |Added

 CC||doug dot gregor at gmail dot
   ||com


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

[Bug c++/36999] Erroneous "declaration 'class ...' does not declare anything" warnings possible

[simon_baldwin at yahoo dot com]

--- Comment #3 from simon_baldwin at yahoo dot com  2008-08-06 12:00 ---
Thanks for the note.  Fixed for trunk; I'm currently in the process of
backporting to the 4.3 branch since the bug is there also.


-- 

simon_baldwin at yahoo dot com changed:

   What|Removed |Added

  Known to fail||4.4.0 4.3.1 4.3.0


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

[Bug c++/36460] No space between >'s not always handled in C++0x

[peterbindels at gmail dot com]

--- Comment #3 from peterbindels at gmail dot com  2008-08-06 11:44 ---
Could anybody at least confirm this bug?


-- 


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

[Bug middle-end/35432] [4.2/4.3/4.4 regression] ICE with zero-sized array

[aldyh at gcc dot gnu dot org]

--- Comment #6 from aldyh at gcc dot gnu dot org  2008-08-06 10:43 ---
Fixed on mainline, 4.3, and 4.2.


-- 

aldyh at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution||FIXED


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

[Bug middle-end/35432] [4.2/4.3/4.4 regression] ICE with zero-sized array

[aldyh at gcc dot gnu dot org]

--- Comment #5 from aldyh at gcc dot gnu dot org  2008-08-06 10:43 ---
Subject: Bug 35432

Author: aldyh
Date: Wed Aug  6 10:41:39 2008
New Revision: 138796

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=138796
Log:
PR middle-end/35432
* gimplify.c (gimplify_modify_expr): Do not optimize zero-sized types
if want_value.
 testsuite/
* gcc.c-torture/compile/pr35432.c: New file.

Added:
branches/gcc-4_2-branch/gcc/testsuite/gcc.c-torture/compile/pr35432.c
Modified:
branches/gcc-4_2-branch/gcc/ChangeLog
branches/gcc-4_2-branch/gcc/gimplify.c
branches/gcc-4_2-branch/gcc/testsuite/ChangeLog


-- 


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

[Bug middle-end/35432] [4.2/4.3/4.4 regression] ICE with zero-sized array

[aldyh at gcc dot gnu dot org]

--- Comment #4 from aldyh at gcc dot gnu dot org  2008-08-06 10:32 ---
Subject: Bug 35432

Author: aldyh
Date: Wed Aug  6 10:31:22 2008
New Revision: 138794

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=138794
Log:
PR middle-end/35432
* gimplify.c (gimplify_modify_expr): Do not optimize zero-sized types
if want_value.
 testsuite/
* gcc.c-torture/compile/pr35432.c: New file.


Added:
branches/gcc-4_3-branch/gcc/testsuite/gcc.c-torture/compile/pr35432.c
Modified:
branches/gcc-4_3-branch/gcc/ChangeLog
branches/gcc-4_3-branch/gcc/gimplify.c
branches/gcc-4_3-branch/gcc/testsuite/ChangeLog


-- 


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

[Bug middle-end/35432] [4.2/4.3/4.4 regression] ICE with zero-sized array

[aldyh at gcc dot gnu dot org]

--- Comment #3 from aldyh at gcc dot gnu dot org  2008-08-06 10:26 ---
Subject: Bug 35432

Author: aldyh
Date: Wed Aug  6 10:25:22 2008
New Revision: 138793

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=138793
Log:
PR middle-end/35432
* gimplify.c (gimplify_modify_expr): Do not optimize zero-sized types
if want_value.
 testsuite/
* gcc.c-torture/compile/pr35432.c: New file.


Added:
trunk/gcc/testsuite/gcc.c-torture/compile/pr35432.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/gimplify.c
trunk/gcc/testsuite/ChangeLog


-- 


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

[Bug tree-optimization/35428] [4.3 regression] ICE with "-ftrapv"

[aldyh at gcc dot gnu dot org]

--- Comment #9 from aldyh at gcc dot gnu dot org  2008-08-06 10:18 ---
I can no longer reproduce this on either the 4.3 branch or mainline.  Volker,
can you check on your end?

If there is no update, I will close at the end of the week.


-- 

aldyh at gcc dot gnu dot org changed:

   What|Removed |Added

 AssignedTo|unassigned at gcc dot gnu   |aldyh at gcc dot gnu dot org
   |dot org |
 Status|REOPENED|ASSIGNED


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

[Bug other/37036] fixincludes does not understand sysroot!

[jayk123 at hotmail dot com]

--- Comment #2 from jayk123 at hotmail dot com  2008-08-06 10:10 ---
uh, no, I used that actually


-- 


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

[Bug other/37036] fixincludes does not understand sysroot!

[jayk123 at hotmail dot com]

--- Comment #1 from jayk123 at hotmail dot com  2008-08-06 10:08 ---
wait, um, maybe -with-build-sysroot= works, with an equals sign. I'll try that.


-- 


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

[Bug middle-end/35432] [4.2/4.3/4.4 regression] ICE with zero-sized array

[aldyh at gcc dot gnu dot org]

--- Comment #2 from aldyh at gcc dot gnu dot org  2008-08-06 10:00 ---
http://gcc.gnu.org/ml/gcc-patches/2008-08/msg00322.html


-- 

aldyh at gcc dot gnu dot org changed:

   What|Removed |Added

 AssignedTo|unassigned at gcc dot gnu   |aldyh at gcc dot gnu dot org
   |dot org |
 Status|NEW |ASSIGNED


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

[Bug other/37036] New: fixincludes does not understand sysroot!

[jayk123 at hotmail dot com]

gcc 4.3.1

given build=platform1 (i686-pc-cygwin)
given platform2 (sparc-sun-solaris2.10) 

mkdir /obj
mkdir /obj/1
cd /obj/1
# ensure up to date native tools
/src/gcc/configure -build platform1 -host platform1 -target platform1
-disable-bootstrap -disable-multilib -enable-languages=c,c++ && make && make
install


# cross tools -- have setup sysroot ahead of time
mkdir /obj/2
cd /obj/2
/src/gcc/configure -build platform1 -host platform1 -target platform2
-disable-bootstrap -disable-multilib -enable-languages=c,c++ && make && make
install

# now the problem part
mkdir /obj/3
cd /obj/3
/src/gcc/configure -build platform1 -host platform2 -target platform2
-disable-bootstrap -disable-multilib -enable-languages=c,c++  && make &&
make install
DESTDIR=/usr/local/platform2/install

tar up the install
scp
untar on host
try it out

errors, because fixincludes uses the build /usr/include instead of the
sys-rooted /usr/include.

Even using -with-build-sysroot /usr/local/platform2/sys-root does not work.
Apparently. I have to go read the code.

Specific workaround:
delete include-fixed/math.h


I think this is particularly problematic in that the requirements here are
"unique". Nowewhere else does the two platform canadian cross need the
host/target sysroot. It's builtin to the cross compiler.

The cross ocmpiler also has the correctly fixed includes.
So another workaround is to use them.
But they might be from an older version of gcc/fixincludes.


-- 
   Summary: fixincludes does not understand sysroot!
   Product: gcc
   Version: unknown
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: other
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jayk123 at hotmail dot com
  GCC host triplet: host=target, host!=build


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

[Bug c++/37029] Exception from shared library's functions or methods that return float (double, long double) value cannot be caught on HP-UX.

[v dot grikyan at sam-solutions dot net]

--- Comment #3 from v dot grikyan at sam-solutions dot net  2008-08-06 
09:11 ---
As we understand (looking at gcc sources), sjlj-mechanism can be set only
during building of gcc.
We did not build gcc on our HP-UX system ourselves but looking at output "gcc
-v" it seems it was configured without any parameters

bash-3.2$ gcc -v
Using built-in specs.
Target: hppa2.0w-hp-hpux11.11
Configured with: ../gcc/configure  : (reconfigured) ../gcc/configure  :
(reconfigured) ../gcc/configure
Thread model: posix
gcc version 4.1.2

So gcc build system had to determine configuration automatically.
We found in .../libstdc++-v3/configure

  --enable-sjlj-exceptions
 force use of builtin_setjmp for exceptions
 [default=auto]

Also in .../gcc-4.1.2/libstdc++-v3/libsupc++/eh_throw.cc we see the following
code

#ifdef _GLIBCXX_SJLJ_EXCEPTIONS
  _Unwind_SjLj_RaiseException (&header->unwindHeader);
#else
  _Unwind_RaiseException (&header->unwindHeader);
#endif

and going through debug of our test application we see the call of the function
_Unwind_RaiseException but not _Unwind_SjLj_RaiseException
So we suppose that dwarf2-mechanism is used.

Also we found in the document "Installing GCC"
(http://209.85.135.104/search?q=cache:crNR9x-pALIJ:wwwcdf.pd.infn.it/localdoc/gccinstall.ps.gz+gcc+sjlj+dwarf2+exceptions+option&hl=ru&ct=clnk&cd=28)
the following phrase

"As of GCC 4.1, DWARF2 exception handling is available on HP-UX. It is now the
default.This exposed a bug in the handling of data relocations in the GAS
assembler. The handlingof 64-bit data relocations was seriously broken,
affecting debugging and exception supporton all 'hppa64-*-*' targets. Under
some circumstances, 32-bit data relocations could alsobe handled incorrectly.
This problem is fixed in GAS version 2.16.91 20051125"

In our case 'as --version' prints the following result

bash-3.2$ as --version
GNU assembler (GNU Binutils) 2.18
Copyright 2007 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or later.
This program has absolutely no warranty.
This assembler was configured for a target of `hppa2.0w-hp-hpux11.11'.

So it seems GAS version is correct but anyway the test application does not
work...


-- 


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

[Bug middle-end/34921] Misalign stack variable referenced by nested function

[Joey dot ye at intel dot com]

--- Comment #9 from Joey dot ye at intel dot com  2008-08-06 08:05 ---
Fixed


-- 

Joey dot ye at intel dot com changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED


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

[Bug bootstrap/37035] New: gcc-4.2.2 build failed on solaris-8

[halder dot malay at gmail dot com]

I am trying to build gcc-4.2.2 on a solaris-8 machine using gcc-3.4.4 

** my build machine details:-
SunOS  5.8 Generic_108528-20 sun4u sparc SUNW,Sun-Blade-100

** my gcc-3.4.4 configuration --> which is used to build new gcc-4.2.2

Configured with: ../gcc-3.4.4/configure
--prefix=/tools/openbin/gcc/3.4.4/sparc-sun-solaris8 --disable-nls
--enable-languages=c,c++,java --enable-shared --enable-threads=posix
--with-gnu-as
--with-as=/tools/openbin/binutils/2.16.1/sparc-sun-solaris8/bin/as
--with-gnu-ld
--with-ld=/tools/openbin/binutils/2.16.1/sparc-sun-solaris8/bin/ld
Thread model: posix
gcc version 3.4.4

** MY CONFIGURE OPTIONS **

--prefix=$(DEST_DIR) \
--disable-nls \
--enable-shared \
--enable-threads=posix \
--with-ld=/usr/ccs/bin/ld\
--with-as=/usr/ccs/bin/as \
--enable-languages=c,c++ \
   
--with-mpfr=/tools/openbin/mpfr/2.3.1/sparc-sun-solaris10 \
   
--with-mpfr-include=/tools/openbin/mpfr/2.3.1/sparc-sun-solaris10/include \
   
--with-mpfr-lib=/tools/openbin/mpfr/2.3.1/sparc-sun-solaris10/lib \
   
--with-gmp=/tools/openbin/gmp/4.2.2/sparc-sun-solaris10 \
   
--with-gmp-lib=/tools/openbin/gmp/4.2.2/sparc-sun-solaris10/lib \
   
--with-gmp-include=/tools/openbin/gmp/4.2.2/sparc-sun-solaris10/include


** i have used solaris native ld && as . because i need a gcc build with
solaris ld for building xemacs in future**


*** ERROR MESSAGES  --> coming in the build stage ***

configure: creating ./config.status
config.status: creating Makefile
config.status: creating testsuite/Makefile
config.status: creating config.h
config.status: executing default commands
gmake[4]: Entering directory
`/users/toolsrd/ws/si_ctoolrd/gcc/production/objects/gcc-4.2.2/build-sparc-sun-solaris2.8/libiberty'
if [ x"" != x ] && [ ! -d pic ]; then \
  mkdir pic; \
else true; fi
touch stamp-picdir
if [ x"" != x ]; then \
  /tools/openbin/gcc/4.2.2/sparc-sun-solaris10/bin/gcc -c -DHAVE_CONFIG_H -g
-I.
-I/users/toolsrd/ws/si_ctoolrd/gcc/production/sources/gcc-4.2.2/libiberty/../include
 -W -Wall -pedantic -Wwrite-strings -Wstrict-prototypes -Wc++-compat 
/users/toolsrd/ws/si_ctoolrd/gcc/production/sources/gcc-4.2.2/libiberty/regex.c
-o pic/regex.o; \
else true; fi
/tools/openbin/gcc/4.2.2/sparc-sun-solaris10/bin/gcc -c -DHAVE_CONFIG_H -g -I.
-I/users/toolsrd/ws/si_ctoolrd/gcc/production/sources/gcc-4.2.2/libiberty/../include
 -W -Wall -pedantic -Wwrite-strings -Wstrict-prototypes -Wc++-compat
/users/toolsrd/ws/si_ctoolrd/gcc/production/sources/gcc-4.2.2/libiberty/regex.c
-o regex.o
In file included from /usr/include/sys/types.h:19,
 from
/users/toolsrd/ws/si_ctoolrd/gcc/production/sources/gcc-4.2.2/libiberty/regex.c:51:
/tools/openbin/gcc/4.2.2/sparc-sun-solaris10/bin/../lib/gcc/sparc-sun-solaris2.10/4.2.2/include/sys/feature_tests.h:20:26:
error: sys/ccompile.h: No such file or directory
In file included from /usr/include/sys/types.h:36,
 from
/users/toolsrd/ws/si_ctoolrd/gcc/production/sources/gcc-4.2.2/libiberty/regex.c:51:
/usr/include/sys/int_types.h:111: error: duplicate 'unsigned'
/users/toolsrd/ws/si_ctoolrd/gcc/production/sources/gcc-4.2.2/libiberty/regex.c:130:
warning: function declaration isn't a prototype
/users/toolsrd/ws/si_ctoolrd/gcc/production/sources/gcc-4.2.2/libiberty/regex.c:130:
warning: conflicting types for built-in function 'malloc'
/users/toolsrd/ws/si_ctoolrd/gcc/production/sources/gcc-4.2.2/libiberty/regex.c:131:
warning: function declaration isn't a prototype
In file included from
/users/toolsrd/ws/si_ctoolrd/gcc/production/sources/gcc-4.2.2/libiberty/regex.c:638:
/users/toolsrd/ws/si_ctoolrd/gcc/production/sources/gcc-4.2.2/libiberty/regex.c:
In function 'byte_regex_compile':
/users/toolsrd/ws/si_ctoolrd/gcc/production/sources/gcc-4.2.2/libiberty/regex.c:2439:
warning: implicit declaration of function 'free'
/users/toolsrd/ws/si_ctoolrd/gcc/production/sources/gcc-4.2.2/libiberty/regex.c:
In function 'byte_re_compile_fastmap':
/users/toolsrd/ws/si_ctoolrd/gcc/production/sources/gcc-4.2.2/libiberty/regex.c:4835:
warning: implicit declaration of function 'abort'
/users/toolsrd/ws/si_ctoolrd/gcc/production/sources/gcc-4.2.2/libiberty/regex.c:4835:
warning: incompatible implicit declaration of built-in function
'abort'/users/toolsrd/ws/si_ctoolrd/gcc/production/sources/gcc-4.2.2/libiberty/regex.c:
In function 'byte_re_match_2_internal':
/users/toolsrd/ws/si_ctoolrd/gcc/production/sources/gcc-4.2.2/libiberty/regex.c:7421:
warning: incompatible implicit declaration of built-in function
'abort'/users/toolsrd/ws/si_ctoolrd/gcc/production/sources/gcc-4.2.2/libiberty/regex.c:
In function 'xregerror':
/users/toolsrd/ws/si_cto