bug in gcj 1:3.2.1-0pre1

2003-01-07 Thread Radim Kolar
i have found bug in gcj, i can not compile my program scache, earlier
versions of scache has been sucessfully compliled.

You can get scache at http://home.worldonline.cz/~cz210552/scache.html

can you try to compile it with latest gcj and report bug to gcc team?

Thanks.

gcj-3.2 -Wall -fno-store-check -O2 -fforce-classes-archive-check --classpath 
/usr/share/java:. --main=scache cacheobject.java mgr.java request.java 
HTUU.java garbage.java regexp.java scache.java cachedir.java httpreq.java 
repair.java InOut.java ui.java uireq.java gnu/rex/Atom.java gnu/rex/Range.java 
gnu/rex/AtomSet.java gnu/rex/AtomString.java gnu/rex/Anchor.java 
gnu/rex/RegExprSyntaxException.java gnu/rex/AtomBackRef.java gnu/rex/Expr.java 
gnu/rex/Parser.java gnu/rex/State.java gnu/rex/State1.java 
gnu/rex/RexResult.java gnu/rex/StateSet.java gnu/rex/StateNSet.java 
gnu/rex/StateAnchor.java gnu/rex/StateCntrl.java gnu/rex/IntPtr.java 
gnu/rex/StateRepeater.java gnu/rex/StateBackRef.java gnu/rex/StateMachine.java
gnu/rex/Rex.java -o scache-native
/tmp/ccgu2Isljx: In class `mgr':
/tmp/ccgu2Isljx: In method `mgr.read_config(java.lang.String)':
/tmp/ccgu2Isljx:879: Internal compiler error in fixup_abnormal_edges, at 
reload1.c:9525
Please submit a full bug report,
with preprocessed source if appropriate.
See http://www.gnu.org/software/gcc/bugs.html> for instructions.




Re: bug in gcj 1:3.2.1-0pre1

2003-01-07 Thread Matthias Klose
Radim Kolar writes:
> i have found bug in gcj,

which exact version?

> i can not compile my program scache, earlier
> versions of scache has been sucessfully compliled.

which earlier versions?

> You can get scache at http://home.worldonline.cz/~cz210552/scache.html
> 
> can you try to compile it with latest gcj and report bug to gcc team?

you can do as well. Please report the results using gcj from the
gcc-snapshot package.

Thanks, Matthias

> Thanks.
> 
> gcj-3.2 -Wall -fno-store-check -O2 -fforce-classes-archive-check --classpath 
> /usr/share/java:. --main=scache cacheobject.java mgr.java request.java 
> HTUU.java garbage.java regexp.java scache.java cachedir.java httpreq.java 
> repair.java InOut.java ui.java uireq.java gnu/rex/Atom.java 
> gnu/rex/Range.java gnu/rex/AtomSet.java gnu/rex/AtomString.java 
> gnu/rex/Anchor.java gnu/rex/RegExprSyntaxException.java 
> gnu/rex/AtomBackRef.java gnu/rex/Expr.java gnu/rex/Parser.java 
> gnu/rex/State.java gnu/rex/State1.java gnu/rex/RexResult.java 
> gnu/rex/StateSet.java gnu/rex/StateNSet.java gnu/rex/StateAnchor.java 
> gnu/rex/StateCntrl.java gnu/rex/IntPtr.java gnu/rex/StateRepeater.java 
> gnu/rex/StateBackRef.java gnu/rex/StateMachine.java
> gnu/rex/Rex.java -o scache-native
> /tmp/ccgu2Isljx: In class `mgr':
> /tmp/ccgu2Isljx: In method `mgr.read_config(java.lang.String)':
> /tmp/ccgu2Isljx:879: Internal compiler error in fixup_abnormal_edges, at 
> reload1.c:9525
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See http://www.gnu.org/software/gcc/bugs.html> for instructions.
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Bug#123468: c/6906: warn about asserts with side effects

2003-01-07 Thread bangerth
Synopsis: warn about asserts with side effects

State-Changed-From-To: open->feedback
State-Changed-By: bangerth
State-Changed-When: Tue Jan  7 17:40:58 2003
State-Changed-Why:
As much as I sympathize with the goal of such a warning, I
doubt it will be possible to implement it. The reason is
that assert() is usually implemented via a macro. On my
system, it reads (if !NDEBUG):

# define assert(expr) \
  (__ASSERT_VOID_CAST ((expr) ? 0 : 
  \
   (__assert_fail (__STRING(expr), __FILE__, __LINE__,  
  \
   __ASSERT_FUNCTION), 0)))
---
so at the time the _compiler_ (as opposed to the
preprocessor) sees the condition, the special name "assert"
is already gone. On the other hand, the preprocessor doesn't
know anything about expressions with or without side effects.

I thus seriously doubt that such a warning can be implemented
without gross hacks...

W.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6906