gcj-mingw is ready for inclusion in gcc 3.1

[Adam Megacz]

Bryce McKinlay <bryce@waitaki.otago.ac.nz> writes:
> I want to add a compiler option which tells it that a given 
> class/package/everything will end up in the same binary object. This 
> will help with binary compatibility optimizations, ie knowing when it is 
> safe to inline a method from another class, use direct field access 
> instead of offset indirection, etc. We can use the same flag to tell the 
> mingw back-end when to use "dllimport".

I've heard rumors of moving towards one .o per package for
libgcj... do you think we could include an option to disable this
behavior in the configury? That way you don't have to rebuild a whole
package when you change just one source file. It would also help me a
lot with my unreachable method stripping stuff.

  - a

-- 
"If I put copyrighted material into the 'chewy nougat center', I can
 claim the crunchy chocolate coating is an 'Access Control
 Mechanism'."                                     --lynx_user_abroad

Why Windows NT/2k/XP is unreliable: www.zappadoodle.com