Is there a diff for GCC 3.4.2? The source distro only includes diffs for 3.3.3 and earlier; Google wasn't much help with the query, either.
-- Political Dissident Neil Santos Free Software Advocate Jabber: nsantos@jabber.org
Please avoid sending me attachments encoded in secret formatting. See http://www.fsf.org/philosophy/no-word-attachments.html
Neil Santos wrote:
Is there a diff for GCC 3.4.2? The source distro only includes diffs for 3.3.3 and earlier; Google wasn't much help with the query, either.
If you ask if gpc-20041017 works with gcc-3.4.x then the answer is no. There are patches for gpc-20040516 at: http://www.math.uni.wroc.pl/~hebisch/gpc
There is a patch for gpc proper and two backend patches. For gcc-3.4.2 the 'gcc-3.4.diff8.gz' patch should work (there is harmless reject). For CVS versions 'gcc-3.4.diff10.gz' is needed.
I would like to see the above patches integrated into a gpc release, but if I understand correctly Frank do not plan to include then in next release. More precisely, gpc-20041017 works quite well on 32-bit machines but fails many test on 64-bit machines (I would say it is just broken on 64-bit machines). AFAIU Frank's anouncement about gpc-20041017 he plans a quick follow-up release -- presumably only adding bug-fixes (please correct if it is wrong).
ATM I do not plan to update 3.4 patches to work with gpc-20041017. Assuming that follow-up is quick enough I will update patches for the follow-up.
Is there a diff for GCC 3.4.2? The source distro only includes diffs for 3.3.3 and earlier; Google wasn't much help with the query, either.
If you ask if gpc-20041017 works with gcc-3.4.x then the answer is no.
Yes, I did mean 20041017, and Damn, I was afraid of that. :D Sorry, I wrote my original message at around 0500 local. Not the best time to be writing mails.
There are patches for gpc-20040516 at: http://www.math.uni.wroc.pl/~hebisch/gpc
Next question: Where then do I get a copy of the source for 20040516? http://www.g-n-u.de/gpc/ only has copies of the latest snapshot.
I'll ask Google, of course; but it's comforting to think that there might be an answer when I download my next batch of mails. ;D
There is a patch for gpc proper and two backend patches. For gcc-3.4.2 the 'gcc-3.4.diff8.gz' patch should work (there is harmless reject). For CVS versions 'gcc-3.4.diff10.gz' is needed.
Waldek, do you mean to say that these aforementioned patches can't be fixed for the latest snapshot? No, I don't mean `not easily', but `impossible'. If it's possible, I'd like to try my hand with trying to fix it--might take my mind off of things for a bit.
ATM I do not plan to update 3.4 patches to work with gpc-20041017. Assuming that follow-up is quick enough I will update patches for the follow-up.
How quick is `quick enough'? :D
-- Political Dissident Neil Santos Free Software Advocate Jabber: nsantos@jabber.org
Please avoid sending me attachments encoded in secret formatting. See http://www.fsf.org/philosophy/no-word-attachments.html
Next question: Where then do I get a copy of the source for 20040516? http://www.g-n-u.de/gpc/ only has copies of the latest snapshot.
Found it! http://www.desy.de/~bohnen/gpc/ has a copy of the gzip'd tarball of the 20040516-dated snapshot, plus a PDF of the GPC manual.
Now... If I could just find a verified MD5 checksum of the official distro, I'll be set...
-- Political Dissident Neil Santos Free Software Advocate Jabber: nsantos@jabber.org
Please avoid sending me attachments encoded in secret formatting. See http://www.fsf.org/philosophy/no-word-attachments.html
Neil Santos wrote:
Next question: Where then do I get a copy of the source for 20040516? http://www.g-n-u.de/gpc/ only has copies of the latest snapshot.
Found it! http://www.desy.de/~bohnen/gpc/ has a copy of the gzip'd tarball of the 20040516-dated snapshot, plus a PDF of the GPC manual.
Now... If I could just find a verified MD5 checksum of the official distro, I'll be set...
See ftp://ftp.u-aizu.ac.jp/pub/gnu/gnu-pascal
Regards,
Adriaan van Os
On 28 Oct 2004 at 17:25, Adriaan van Os wrote:
Neil Santos wrote:
Next question: Where then do I get a copy of the source for 20040516? http://www.g-n-u.de/gpc/ only has copies of the latest snapshot.
Found it! http://www.desy.de/~bohnen/gpc/ has a copy of the gzip'd tarball of the 20040516-dated snapshot, plus a PDF of the GPC manual.
Now... If I could just find a verified MD5 checksum of the official distro, I'll be set...
Nice site! Seems to have mirrored a lot of the GPC web site.
Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) web: http://www.greatchief.plus.com/
Neil Santos wrote:
There is a patch for gpc proper and two backend patches. For gcc-3.4.2 the 'gcc-3.4.diff8.gz' patch should work (there is harmless reject). For CVS versions 'gcc-3.4.diff10.gz' is needed.
Waldek, do you mean to say that these aforementioned patches can't be fixed for the latest snapshot? No, I don't mean `not easily', but `impossible'. If it's possible, I'd like to try my hand with trying to fix it--might take my mind off of things for a bit.
I have created the patches so it is `possible'. In fact adjusting patches for new gpc version should be much easier then creating them in the first place. The "algorithm" I use is: -- try which part can be applied mechanically -- go trough diff and find places where the other hunks should go and insert code from diff there -- go trough diff between gpc-20041017 and gpc-20040516 and find new places which should be updated. Also look for possible errors which first (mechanical) stage could introduce -- run the testsuite and fix all errors (if any).
My experience was that that most of places where diff was not able to apply a hunks still was passible to resolve without deep understanding of the code. A few place may require going trough larger parts of the sources to find needed information.
What skills are needed? Knowledge of C. Probably reading GCC internals manual. Also
http://cobolforgcc.sourceforge.net/cobol_14.html
may be usefull (it is somewhat outdated). And general knowledge about compilers is usefull.
If you want to "get into" GPC/GCC developement than updating the diff may be a good starting point. On the other hand changing the compiler without understanding is likely to introduce bugs, so at the beginning most of the effort must go into learning how the compiler works. I estimate that updating patches will take me 1-2 days. Somebody familiar with C but unfamiliar with GPC/GCC probably needs about a week to modify compiler with confidence (the keyword here is confidence, most changes are mechanical and in few other cases one can get working compiler just by pure luck). If you do not know C then I would say: forget about touching the patches.
ATM I do not plan to update 3.4 patches to work with gpc-20041017. Assuming that follow-up is quick enough I will update patches for the follow-up.
How quick is `quick enough'? :D
2-3 weeks from now.