Message ID | 53F5250D.4030301@oarcorp.com |
---|---|
State | Committed |
Headers |
Received: (qmail 10236 invoked by alias); 20 Aug 2014 22:45:43 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: <gdb-patches.sourceware.org> List-Unsubscribe: <mailto:gdb-patches-unsubscribe-##L=##H@sourceware.org> List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org> List-Archive: <http://sourceware.org/ml/gdb-patches/> List-Post: <mailto:gdb-patches@sourceware.org> List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs> Sender: gdb-patches-owner@sourceware.org Delivered-To: mailing list gdb-patches@sourceware.org Received: (qmail 10208 invoked by uid 89); 20 Aug 2014 22:45:38 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL, BAYES_00, RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: OARmail.OARCORP.com Received: from oarmail.oarcorp.com (HELO OARmail.OARCORP.com) (67.63.146.244) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 20 Aug 2014 22:45:36 +0000 Received: from [192.168.1.169] (192.168.1.169) by OARmail.OARCORP.com (192.168.2.2) with Microsoft SMTP Server (TLS) id 8.3.342.0; Wed, 20 Aug 2014 17:39:10 -0500 Message-ID: <53F5250D.4030301@oarcorp.com> Date: Wed, 20 Aug 2014 17:45:33 -0500 From: Joel Sherrill <joel.sherrill@oarcorp.com> User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org> Subject: Fix spelling error in psim Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit |
Commit Message
Joel Sherrill
Aug. 20, 2014, 10:45 p.m. UTC
Hi OK to commit as obvious? 2014-08-21 Joel Sherrill <joel.sherrill@oarcorp.com> * ppc-instructions: Fix spelling error. case spr_tbu:
Comments
On Wed, Aug 20, 2014 at 3:45 PM, Joel Sherrill <joel.sherrill@oarcorp.com> wrote: > > Hi > > OK to commit as obvious? > > 2014-08-21 Joel Sherrill <joel.sherrill@oarcorp.com> > > * ppc-instructions: Fix spelling error. > > diff --git a/sim/ppc/ppc-instructions b/sim/ppc/ppc-instructions > index 1b8fd89..1a2e51a 100644 > --- a/sim/ppc/ppc-instructions > +++ b/sim/ppc/ppc-instructions > @@ -3355,7 +3355,7 @@ void::function::invalid_zero_divide_operation:cpu > *proces > spreg new_val = (spr_length(n) == 64 > ? *rS > : MASKED(*rS, 32, 63)); > - /* HACK - time base registers need to be updated immediatly */ > + /* HACK - time base registers need to be updated immediately */ > if (WITH_TIME_BASE) { > switch (n) { > case spr_tbu: Yep. [If this were gdb one might want a "." followed by two spaces here, but this isn't gdb. Lucky you. :-)]
On Wed 20 Aug 2014 17:45:33 Joel Sherrill wrote:
> OK to commit as obvious?
certainly. i'd point out that `git grep immediatly` shows a bunch more hits
too :).
-mike
On Wed 20 Aug 2014 17:10:36 Doug Evans wrote: > [If this were gdb one might want a "." followed by two spaces here, > but this isn't gdb. Lucky you. :-)] that's enforced in new code (which psim is anything but). i'd have no problem if someone felt like going through and cleaning that particular issue up in the whole code base. sim should be following GNU style conventions. i dislike them, but it's part of a larger GNU project, so deviating anyways would be bad form :). -mike
> > [If this were gdb one might want a "." followed by two spaces here, > > but this isn't gdb. Lucky you. :-)] > > that's enforced in new code (which psim is anything but). i'd have no > problem if someone felt like going through and cleaning that > particular issue up in the whole code base. > > sim should be following GNU style conventions. i dislike them, but > it's part of a larger GNU project, so deviating anyways would be bad > form :). Interestingly, I have always considered sim to be part of the GDB project, and therefore under GDB coding style.
On Thu 21 Aug 2014 09:15:35 Joel Brobecker wrote: > > > [If this were gdb one might want a "." followed by two spaces here, > > > but this isn't gdb. Lucky you. :-)] > > > > that's enforced in new code (which psim is anything but). i'd have no > > problem if someone felt like going through and cleaning that > > particular issue up in the whole code base. > > > > sim should be following GNU style conventions. i dislike them, but > > it's part of a larger GNU project, so deviating anyways would be bad > > form :). > > Interestingly, I have always considered sim to be part of the GDB > project, and therefore under GDB coding style. aren't they the same thing ? i guess let's see. gdb/CONTRIBUTE says: o Coding Standards All contributions must conform to the GNU Coding Standard. Submissions which do not conform to the standards will be returned with a request to reformat the changes. which is what i thought ... but then there's this follow up: GDB has certain additional coding requirements. Those requirements are explained in the GDB internals documentation in the gdb/doc directory. except there's no gdbint.texinfo anymore. let's check the website: https://www.gnu.org/software/gdb/documentation/ GDB Internals Manual (wiki only) https://sourceware.org/gdb/wiki/InternalsManual https://sourceware.org/gdb/wiki/Internals%20GDB-C-Coding-Standards ok, i guess there's a few more rules here. having the sim follow those is fine. -mike
On 8/21/2014 2:15 AM, Joel Brobecker wrote: >>> [If this were gdb one might want a "." followed by two spaces here, >>> but this isn't gdb. Lucky you. :-)] >> that's enforced in new code (which psim is anything but). i'd have no >> problem if someone felt like going through and cleaning that >> particular issue up in the whole code base. >> >> sim should be following GNU style conventions. i dislike them, but >> it's part of a larger GNU project, so deviating anyways would be bad >> form :). > Interestingly, I have always considered sim to be part of the GDB > project, and therefore under GDB coding style. > Let me fix the spelling issues first. Is that OK? I am not opposed to fixing the style issues but really don't have to get sucked into them right now. Can uncrustify or some other tool help?
> Let me fix the spelling issues first. Is that OK? > > I am not opposed to fixing the style issues but really don't have to get > sucked into them right now. That would be absolutely fine. The fact that you are improving one area does not mean that you are then responsible for making that particular area perfect.
diff --git a/sim/ppc/ppc-instructions b/sim/ppc/ppc-instructions index 1b8fd89..1a2e51a 100644 --- a/sim/ppc/ppc-instructions +++ b/sim/ppc/ppc-instructions @@ -3355,7 +3355,7 @@ void::function::invalid_zero_divide_operation:cpu *proces spreg new_val = (spr_length(n) == 64 ? *rS : MASKED(*rS, 32, 63)); - /* HACK - time base registers need to be updated immediatly */ + /* HACK - time base registers need to be updated immediately */ if (WITH_TIME_BASE) { switch (n) {