Mail Archives: djgpp/2002/09/09/08:15:10
Well, as for the newline problem, I wasn't sure whether or not it was
a GCC or a DJGPP problem, so I came here to ask. Nothing wrong with
that. I'm not persisting to blame DJGPP for this stuff or anything.
The main reason I was confused is that SunOS gcc 2.95.3 doesn't seem
to care about the new line thing. So either that's older than the
version of gcc now shipping with DJGPP (somebody clue me in here :P),
or there's some other odd difference. I dunno.
Anyways, I've decided to keep on supporting DJGPP and I hope that if I
can keep my source compliant enough on a change-by-change basis that
these big huge issues won't come up quite as often.
James
On 7 Sep 2002 12:48:45 GMT, eplmst AT lu DOT erisoft DOT se (Martin Stromberg)
wrote:
>James Haley (haleyjd AT NOSPAM DOT hotmail DOT com) wrote:
>: Some examples of problems he's had:
>: * "const" modifier on inline asm block disappeared after GCC 3.03
>: * major changes to register clobbering rules required total rewrite of
>: all inline assembly in the program (fortunately I know someone who
>: knows x86 assembly very well, because I personally do not)
>: * sudden addition of newline requirement
>
>: And a few other things I've forgotten.
>
>: So that, in short, is my frustration. I've enjoyed using DJGPP in the
>: past but I've found maintenance to be more difficult than I'd expect.
>
>This isn't because of DJGPP. It's because of GCC. So I suggest you
>complain to them and not to us.
>
>If there's something that the DJGPP port of GCC broke (i. e. it works
>on other platforms but not DJGPP), then you're welcome to complain
>here.
>
>
>Right,
>
> MartinS
- Raw text -