--- Comment #6 from steven at gcc dot gnu dot org 2007-04-17 22:09 ---
.
--
steven at gcc dot gnu dot org changed:
What|Removed |Added
Status|RESOLVED
--- Comment #5 from deji_aking at yahoo dot ca 2007-04-17 13:21 ---
Yes adding compiling with -ffixed-line-length-80 solved the issue for me,
thanks to you both. I've noticed the original author of that code used tabs in
a couple of space he should have used spaces, the other compilers I
--- Comment #4 from tobi at gcc dot gnu dot org 2007-04-17 12:14 ---
(In reply to comment #3)
> To the reporter:
> Even though this is already (correctly) closed as INVALID, please let us know
> if your code does compile and run correctly if you compile with the suggested
> extra command
--- Comment #3 from steven at gcc dot gnu dot org 2007-04-17 07:12 ---
To the reporter:
Even though this is already (correctly) closed as INVALID, please let us know
if your code does compile and run correctly if you compile with the suggested
extra command line option, -ffixed-line-leng
--- Comment #2 from tobi at gcc dot gnu dot org 2007-04-17 01:20 ---
Your lines are too wide, hoping that bugzilla will not mess up the formatting
I'll quote an example:
1 2 3 4 5 6 7
12345678901234567890123456789012345678901234567
--- Comment #1 from deji_aking at yahoo dot ca 2007-04-16 23:07 ---
Created an attachment (id=13374)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13374&action=view)
testcase (cut and paste from original)
I can provide the whole file if necessary
--
http://gcc.gnu.org/bugzill
