On Sun, 2014-02-02 at 22:43 -0500, Brian Davis wrote: > Brian Drummond wrote: > > > >> Can you apply this patch over a clean 0.31 > https://sourceforge.net/p/ghdl-updates/code/ci/74c33ea9f3bcaf833c6683114a4d90c8684cfff2/ > > > > A quick test of the indexing testcases in ticket #9 shows the abnormal > exception is gone. > > Bug 16782 also now runs OK. > > While the error messages remain less helpful than the gcc equivalent, > that seems to be a present shortcoming of the mcode version.
Worth keeping the ticket open for that. > I'll put a zip file together after I double check[1] my build and run > it against the full test suite. > > > > > This round of (binary/package/port) releases is based > > on the 0.31 source package plus the MINIMUM set of > > patches required to successfully build each OS package. > > <snip> > > none of these are added to the 0.31 branch. > > > > Two release build questions relating the above comment to Adam: > > Q1) If we're not adding the various OS patches to the 0.31 branch to > create a 0.31.1 tag, then what exactly should I call this thing? > 0.31.1 ? 0.31-mcode-windows-patched ? 0.31-mingw perhaps? > Q2) Is it sufficient to include the final patch file in the release zip > file, or should it be checked in somewhere else? In the zip is fine. > Also note, that 74c33e changeset has libraries.adb edits that don't > apply to 0.31 Okay, so placing the actual patch here <[email protected]> would be good so there's a public record of it even if we don't "maintain" the 0.31 branch any further. - Brian _______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
