This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

EGCS 1.1.1 builds okay on m68k-next-nextstep3 (some 1.1 bugs remain)


I'm pleased to report that EGCS 1.1.1 compiles fine on the
m68k-next-nextstep3 platform.

Checking through bugs I have reported, I see that some bugs have been
fixed and some have not, namely:

    Message-Id: <199808280941.CAA22077@daisy.css.sfu.ca>
    Subject: class ``implementation'' info not always generated...
    Status: Fixed!

    Message-Id: <199809050209.TAA27108@daisy.css.sfu.ca>
    Subject: Exceptions workaround for older systems that don't USE_COLLECT2
    Status: Unfixed. (But fixed on main EGCS branch. My patches for EGCS 1.1
    		(see <199809192231.PAA25870@aldrington.ppp.cs.sfu.ca>)
		also work on EGCS 1.1.1 ).

    Message-Id: <199809200655.XAA26965@aldrington.ppp.cs.sfu.ca>
    Subject: [...] making exceptions safe under cthreads
    Status: Unfixed. (I have some ideas for a fix here, and hopefully my
    		ideas won't upset people the way my original ideas did.)

    Message-Id: <199810070033.RAA20981@aldrington.ppp.cs.sfu.ca>
    Subject: G++ -frepo bug for templates that invoke templates
    Status: Unfixed.

    Message-Id: <199810220359.UAA12380@aldrington.ppp.cs.sfu.ca>
    Subject: M68k Codegen Bug with -frerun-loop-opt, various EGCS versions
    Status: Unfixed.

Only the last one is a serious bug, IMHO, because it generates bad code
that may go undetected.

I can't say whether the latter two bugs are fixed on the main branch
because the main branch seems to have been dying on m68k platforms for
the last several snapshots.

Regards,

    Melissa.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]