On Fri, Jun 30, 2000 at 06:29:11AM -0700, Andrey A. Chernov wrote:
On Wed, Jun 28, 2000 at 11:03:22PM -0700, Andrey A. Chernov wrote:
Fresh -current kernel with fresh -current bootblocks loaded ok but hangs in
boot (no diagnostics even printed, just silent hang with "/" on the screen).
David O'Brien wrote:
On Fri, Jun 30, 2000 at 06:29:11AM -0700, Andrey A. Chernov wrote:
The reason found. I have "-O2 pipe" instead of default "-O pipe", but I have
it working all the time from very beginning. Why this becomes broken?
Because the code change now triggers one of the bugs
On Fri, Jun 30, 2000 at 06:29:11AM -0700, Andrey A. Chernov wrote:
On Wed, Jun 28, 2000 at 11:03:22PM -0700, Andrey A. Chernov wrote:
Fresh -current kernel with fresh -current bootblocks loaded ok but hangs in
boot (no diagnostics even printed, just silent hang with "/" on the screen).
On Wed, Jun 28, 2000 at 11:03:22PM -0700, Andrey A. Chernov wrote:
Fresh -current kernel with fresh -current bootblocks loaded ok but hangs in
boot (no diagnostics even printed, just silent hang with "/" on the screen).
Kernel from Jun14 with fresh -current bootblocks (i.e. the same
On Fri, Jun 30, 2000 at 06:29:11AM -0700, Andrey A. Chernov wrote:
The reason found. I have "-O2 pipe" instead of default "-O pipe", but I have
it working all the time from very beginning. Why this becomes broken?
Because the code change now triggers one of the bugs that has made us
always
David O'Brien wrote:
Because the code change now triggers one of the bugs that has made us
always say "don't use anything above -O".
But, it's still OK to use -march=pentium, though. I'd hate to be
using 386 instructions. 8-)
--
- Donn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
Fresh -current kernel with fresh -current bootblocks loaded ok but hangs in
boot (no diagnostics even printed, just silent hang with "/" on the screen).
Kernel from Jun14 with fresh -current bootblocks (i.e. the same bootblocks)
booted Ok.
--
Andrey A. Chernov
[EMAIL PROTECTED]
