mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Horst H. von Brand" <vonbrand@inf.utfsm.cl>
To: "D. Hazelton" <dhazelton@enter.net>
Cc: Adrian Bunk <bunk@stusta.de>,
	Alistair John Strachan <s0348365@sms.ed.ac.uk>,
	"Zhang, Yanmin" <yanmin_zhang@linux.intel.com>,
	LKML <linux-kernel@vger.kernel.org>, Greg KH <greg@kroah.com>,
	Chuck Ebbert <76306.1226@compuserve.com>,
	Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: kernel + gcc 4.1 = several problems
Date: Tue, 02 Jan 2007 23:05:47 -0300	[thread overview]
Message-ID: <200701030205.l0325lki008679@laptop13.inf.utfsm.cl> (raw)
In-Reply-To: Message from "D. Hazelton" <dhazelton@enter.net>  of "Tue, 02 Jan 2007 18:41:33 CDT." <200701021841.34002.dhazelton@enter.net>

D. Hazelton <dhazelton@enter.net> wrote:

[...]

> None. I didn't file a report on this because I didn't find the big, just
> noted a problem that appears to occur. In this case the call's generated
> seem to wrap loops - something I've never heard of anyone doing.

Example code showing this weirdness?

>                                                                  These
> *might* be causing the off-by-one that is causing the function to
> re-enter in the middle of an instruction.

If something like this happened, programs would be crashing left and right.

> Seeing this I'd guess that this follows for all system-level code
> generated by 4.1.1

Define "system-level code". What makes it different from, say,
bog-of-the-mill compiler code (yes, gcc compiles itself as part of its
sanity checking)?

>                    and this is exactly what I was reporting. If you'd
> like I'll go dig up the dumps he posted and post the two related segments
> side-by-side to give you a better example what I'm referring to.

If the related segments show code that is somehow wrong, by all means
report it /with your detailed analysis/ to the compiler people. Just a
warning, gcc is pretty smart in what it does, its code is often surprising
to the unwashed. Also, the C standard is subtle, the error might be in a
unwarranted assumption in the source code.

  reply	other threads:[~2007-01-03  2:07 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-20 14:21 Oops in 2.6.19.1 Alistair John Strachan
2006-12-20 16:30 ` Greg KH
2006-12-20 16:44   ` Alistair John Strachan
2006-12-23 15:40 ` Alistair John Strachan
2006-12-27  2:07   ` Zhang, Yanmin
2006-12-27 12:35     ` Alistair John Strachan
2006-12-28  2:41       ` Zhang, Yanmin
2006-12-28  4:02         ` Alistair John Strachan
2006-12-28  4:14           ` Alistair John Strachan
2006-12-30 16:59             ` Alistair John Strachan
2006-12-31 13:47               ` Alistair John Strachan
2006-12-31 16:27               ` Adrian Bunk
2006-12-31 16:55                 ` Alistair John Strachan
2007-01-02 21:10                   ` kernel + gcc 4.1 = several problems Adrian Bunk
2007-01-02 21:56                     ` Alistair John Strachan
2007-01-02 22:06                       ` D. Hazelton
2007-01-02 23:24                         ` Adrian Bunk
2007-01-02 23:41                           ` D. Hazelton
2007-01-03  2:05                             ` Horst H. von Brand [this message]
2007-01-02 22:13                       ` Linus Torvalds
2007-01-02 23:18                         ` Alistair John Strachan
2007-01-03  1:43                           ` Linus Torvalds
2007-01-02 22:01                     ` Linus Torvalds
2007-01-02 23:09                       ` David Rientjes
2007-01-03  2:12 Mikael Pettersson
2007-01-03  2:20 ` Alistair John Strachan
2007-01-05 15:53   ` Alistair John Strachan
2007-01-05 16:02     ` Linus Torvalds
2007-01-05 16:19       ` Alistair John Strachan
2007-01-05 16:49         ` Linus Torvalds
2007-01-07  0:36           ` Pavel Machek
2007-01-07  0:57             ` Alistair John Strachan
2007-01-03  5:55 ` Willy Tarreau
2007-01-03 10:29 ` Alan
2007-01-03 10:32   ` Grzegorz Kulewski
2007-01-03 11:51     ` Jeff Garzik
2007-01-03 12:44     ` Alan
2007-01-03 13:32       ` Arjan van de Ven
2007-01-03 13:58         ` Jakub Jelinek
2007-01-03 14:28         ` Alan
2007-01-03 16:06           ` Linus Torvalds
2007-01-03 16:03     ` Linus Torvalds
2007-01-03 17:01       ` l.genoni
2007-01-03 17:45         ` Tim Schmielau
2007-01-03 20:24           ` Linus Torvalds
2007-01-03 17:06       ` l.genoni
2007-01-03 17:53       ` Mariusz Kozlowski
2007-01-03 19:47       ` Denis Vlasenko
2007-01-03 20:38         ` Linus Torvalds
2007-01-03 21:48           ` Denis Vlasenko
2007-01-03 22:13             ` Linus Torvalds
2007-01-03 21:44       ` Thomas Sailer
2007-01-03 22:08         ` Linus Torvalds
2007-01-04  3:08       ` Zou, Nanhai
2007-01-04 15:34         ` Linus Torvalds
2007-01-04  7:11 Albert Cahalan
2007-01-04 16:43 ` Segher Boessenkool
2007-01-04 17:04   ` Albert Cahalan
2007-01-04 17:24     ` Segher Boessenkool
2007-01-04 17:47       ` Linus Torvalds
2007-01-04 18:53         ` Segher Boessenkool
2007-01-04 19:10         ` Al Viro
2007-01-05 17:17       ` Pavel Machek
2007-01-06  8:23         ` Segher Boessenkool
2007-01-04 17:37     ` Linus Torvalds
2007-01-04 18:34       ` Segher Boessenkool
2007-01-04 22:02         ` Geert Bosch
2007-01-07  4:25       ` Denis Vlasenko
2007-01-07  4:45         ` Linus Torvalds
2007-01-07  5:26           ` Jeff Garzik
2007-01-07 15:10         ` Segher Boessenkool
2007-01-26 22:05           ` Michael K. Edwards
2007-01-04 18:08     ` Andreas Schwab

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200701030205.l0325lki008679@laptop13.inf.utfsm.cl \
    --to=vonbrand@inf.utfsm.cl \
    --cc=76306.1226@compuserve.com \
    --cc=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=dhazelton@enter.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s0348365@sms.ed.ac.uk \
    --cc=torvalds@osdl.org \
    --cc=yanmin_zhang@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®