Mike Smith m...@smith.net.au writes:
I usually keep -O to just '-O' - I had been upping it recently, but then
it
started breaking even some of my simple programs, so leasson learn't, it's
staying at just '-O' from now on in... (safety first? :-)
-O2 works fine too. -O3 does not.
On Tue, 16 Feb 1999, Mikhail Teterin wrote:
I usually keep -O to just '-O' - I had been upping it recently, but then it
started breaking even some of my simple programs, so leasson learn't, it's
staying at just '-O' from now on in... (safety first? :-)
-O2 works fine too. -O3 does not.
At 8:05 pm -0800 16/2/99, Mike Smith wrote:
[...]
No, -O2 does not work fine; we've seen reports of it breaking things
before.
I've been using -O2 building -current for over a year with no problems. I
haven't dared try it for the kernel though...
--
Bob Bishop (0118) 977 4017
Bob Bishop wrote:
At 8:05 pm -0800 16/2/99, Mike Smith wrote:
[...]
No, -O2 does not work fine; we've seen reports of it breaking things
before.
I've been using -O2 building -current for over a year with no problems. I
haven't dared try it for the kernel though...
Lucky you. -O2 *does*
:At 8:05 pm -0800 16/2/99, Mike Smith wrote:
:[...]
:No, -O2 does not work fine; we've seen reports of it breaking things
:before.
:
:I've been using -O2 building -current for over a year with no problems. I
:haven't dared try it for the kernel though...
:
:--
:Bob Bishop (0118) 977
On Thu, 18 Feb 1999, Daniel C. Sobral wrote:
Lucky you. -O2 *does* break world for many people. Eventually, it
might break your world too, and there is a great chance you'll first
spam -current before changing -O2 to -O and trying again. Or there
would, if we stopped hitting on this nail. :-)
Matthew Dillon wrote:
I've been using -O2 kernels for over a year. Works fine as far as I
can tell.
I've had a few failures with -O2 ages ago, though I can't guess how long ages
was - I definitely remember tracing one problem down to '-O' vs. '-O2', I
stick to '-0' now
Here is output (checked 2 times) :(
?
=== share/doc/psd/title
touch _stamp.extraobjs
(cd /usr/obj/src/share/doc/psd/title; groff -mtty-char -Tascii -ms -o1-
/usr/obj/src/share/doc/psd/title/Title) |? gzip -cn Title.ascii.gz
groff: can't find `DESC' file
groff:fatal error: invalid device `ascii'
=== share/doc/psd/title
touch _stamp.extraobjs
(cd /usr/obj/src/share/doc/psd/title; groff -mtty-char -Tascii -ms -o1-
/usr/obj/src/share/doc/psd/title/Title) |_ gzip -cn Title.ascii.gz
groff: can't find `DESC' file
groff:fatal error: invalid device `ascii'
This has
Luke wrote:
=== share/doc/psd/title
[snip]
groff: can't find `DESC' file
groff:fatal error: invalid device `ascii'
This has happened to me many times with various versions of current
and
3.x , and its always fixed by lowering the -O# # , I don't know why I just
know
it
I usually keep -O to just '-O' - I had been upping it recently, but then it
started breaking even some of my simple programs, so leasson learn't, it's
staying at just '-O' from now on in... (safety first? :-)
-O2 works fine too. -O3 does not. We'll probably see the newer version
of compiler
Maxim Sobolev wrote:
Here is output (checked 2 times) :(
groff: can't find `DESC' file
groff:fatal error: invalid device `ascii'
[super-snip]
| groff -mtty-char -Tascii -t -s -me -o1- /dev/null
groff: can't find `DESC' file
groff:fatal error: invalid device `ascii'
Ugh, did you have
I usually keep -O to just '-O' - I had been upping it recently, but then it
started breaking even some of my simple programs, so leasson learn't, it's
staying at just '-O' from now on in... (safety first? :-)
-O2 works fine too. -O3 does not. We'll probably see the newer version
of
13 matches
Mail list logo
