On Mon, 20 Jan 2025, 03:27 Chris Clayton via Gcc, wrote:
> Hi
>
> Commit 017c45fa2a4da40893f0aacd96164f04c78cb245 bumped BASE-VER to 15.0.1,
> but the commit message says it's been bumped
> to 14.0.1. I guess it will obvious to readers that it's a typo, but want
> to fix it.44.
>
> Chris
>
Git c
Hi
Commit 017c45fa2a4da40893f0aacd96164f04c78cb245 bumped BASE-VER to 15.0.1, but
the commit message says it's been bumped
to 14.0.1. I guess it will obvious to readers that it's a typo, but want to fix
it.44.
Chris
I've found some typos, etc. in chapter 1 ("About This Guide") of the
GNAT Reference Manual.
Here they come in order of appearance:
#1
This manual contains useful information in writing programs using the
GNAT compiler.
s/in writing/on writing
#2
It includes
201, 80634 München
Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Frank
Thürauf
commit 2044a3e3e8343d047344523a1cca98309ce68fdc
Author: Tobias Burnus
Date: Tue May 25 09:17:07 2021 +0200
fortran/intrinsic.texi: Fix copy'n'paste errors and typos
g
Thanks for reporting the typo. I have now fixed it together with some
other typos.
Tobias
On 8/2/20 10:27 PM, Jonathan Wakely via Fortran wrote:
CC The gfortran list.
On Sat, 1 Aug 2020 at 23:38, Nino Pereira via Gcc wrote:
https://gcc.gnu.org/onlinedocs/gfortran/INT.html#INT
has two
entions.
> http://gcc.gnu.org/codingconventions.html
As explained on that page, certain files and directories come from
upstream and so it is inappropriate to apply GCC-specific conventions to
them, or to fix any typos locally rather than upstream. In particular,
you should not be patching boehm-gc
On Mon, 2013-07-08 at 16:12 +0200, Ondřej Bílka wrote:
> On Sun, Jul 07, 2013 at 09:57:05PM +0200, Oleg Endo wrote:
> > On Sun, 2013-07-07 at 19:54 +0200, Georg-Johann Lay wrote:
> > > Ondrej Bilka schrieb:
> > >
> > > > http://kam.mff.cuni.cz/~ondra/gcc_misspell.patch
> > >
> I fixed most comment
On Mon, Jul 08, 2013 at 10:29:17AM +0100, Jonathan Wakely wrote:
> On 8 July 2013 01:29, Ryan Hill wrote:
> > On Sun, 07 Jul 2013 21:57:05 +0200
> > Oleg Endo wrote:
> >
> >
> >> - // Randomize the colour, just for asthetics =)
> >> + // Randomize the colour, just for aesthetics =)
> >>
> >> ->
On Sun, Jul 07, 2013 at 09:57:05PM +0200, Oleg Endo wrote:
> On Sun, 2013-07-07 at 19:54 +0200, Georg-Johann Lay wrote:
> > Ondrej Bilka schrieb:
> >
> > > http://kam.mff.cuni.cz/~ondra/gcc_misspell.patch
> >
I fixed most comments, put it here so you can diff these two files.
http://kam.mff.cuni.c
On Sun, Jul 07, 2013 at 07:54:34PM +0200, Georg-Johann Lay wrote:
> Ondrej Bilka schrieb:
>
> >http://kam.mff.cuni.cz/~ondra/gcc_misspell.patch
>
> This is wrong:
>
> @@ -10834,7 +10834,7 @@ avr_convert_to_type (tree type, tree expr)
> XOP[2] # Bytes to copy
>
> Return TRUE if the exp
On 8 July 2013 01:29, Ryan Hill wrote:
> On Sun, 07 Jul 2013 21:57:05 +0200
> Oleg Endo wrote:
>
>
>> - // Randomize the colour, just for asthetics =)
>> + // Randomize the colour, just for aesthetics =)
>>
>> -> missed 'color' (in a couple of places actually)
>
> Because that's the correct way
On Sun, Jul 07, 2013 at 04:21:15PM +0200, Ondřej Bílka wrote:
> On Sat, Jul 06, 2013 at 01:14:38PM +0100, Jonathan Wakely wrote:
> > I decided to grep for all the misspelled words beginning with A from
> > your list and fix the ones that were real errors. That took me an hour
> > to produce this pa
On Sun, 07 Jul 2013 21:57:05 +0200
Oleg Endo wrote:
> - // Randomize the colour, just for asthetics =)
> + // Randomize the colour, just for aesthetics =)
>
> -> missed 'color' (in a couple of places actually)
Because that's the correct way of spelling colour.
--
Ryan Hill
On Sun, 2013-07-07 at 19:54 +0200, Georg-Johann Lay wrote:
> Ondrej Bilka schrieb:
>
> > http://kam.mff.cuni.cz/~ondra/gcc_misspell.patch
>
Below are some other hunks that look suspicious...
(trying not to duplicate the things already mentioned by others)
- * 1) It means that finalizers, and al
Ondrej Bilka schrieb:
http://kam.mff.cuni.cz/~ondra/gcc_misspell.patch
This is wrong:
@@ -10834,7 +10834,7 @@ avr_convert_to_type (tree type, tree expr)
XOP[2] # Bytes to copy
Return TRUE if the expansion is accomplished.
- Return FALSE if the operand compination is not supported
On 7 July 2013 15:21, Ondřej Bílka wrote:
>
> discontiguousdiscontinuous
This one is incorrect - the libstdc++ header is talking about
contiguous memory, not continuous memory (arguably it should be
non-contiguous, but leaving it alone is better than changing it to
discontinuous.)
On 7 July 2013 15:21, Ondřej Bílka wrote:
>
> I worked how to make this more efficient. I created patch with obvious cases
> in hour. (only comments in c files though.)
>
> http://kam.mff.cuni.cz/~ondra/gcc_misspell.patch
Some of the code fixed by that (boehm-gc, zlib, libsanitizer) is
maintained
On Sat, Jul 06, 2013 at 01:14:38PM +0100, Jonathan Wakely wrote:
> I decided to grep for all the misspelled words beginning with A from
> your list and fix the ones that were real errors. That took me an hour
> to produce this patch. It doesn't include changes to java or fortran,
> as I don't have
On Fri, Jul 05, 2013 at 05:17:54PM +0100, Jonathan Wakely wrote:
> On 5 July 2013 16:43, Ondřej Bílka wrote:
> >
> > Hi, I ran aspell on comments in gcc. After bit of cleaning a list with
> > frequencies is here. It is still relatively noisy and more heuristics
> > are needed.
> >
> > http://kam.mf
On 5 July 2013 16:43, Ondřej Bílka wrote:
>
> Hi, I ran aspell on comments in gcc. After bit of cleaning a list with
> frequencies is here. It is still relatively noisy and more heuristics
> are needed.
>
> http://kam.mff.cuni.cz/~ondra/gcc_misspells
>
> What we will do with this now?
It doesn't l
On Thu, Jul 04, 2013 at 11:04:32AM +0100, Jonathan Wakely wrote:
> On 4 July 2013 08:20, Marc Glisse wrote:
> >
> > The script could do with some improvements, but it would be good indeed to
> > fix some of those typos.
> >
> > - the script creates non-word
Hi,
On Thu, Jul 04, 2013 at 04:43:00AM +0200, Veres Lajos wrote:
> On Wed, 3 Jul 2013, Veres Lajos wrote:
>
> > Around 99% of the typos are in comments and documentations a few of them
> > are only in function/variable names (living code).
> > I think it is not
On 4 July 2013 08:20, Marc Glisse wrote:
>
> The script could do with some improvements, but it would be good indeed to
> fix some of those typos.
>
> - the script creates non-words : suppresss
Yes, I noticed "functino" being changed to "functiono" :-)
&
On Thu, 4 Jul 2013, Veres Lajos wrote:
On Wed, 3 Jul 2013, Veres Lajos wrote:
Around 99% of the typos are in comments and documentations a few of them
are only in function/variable names (living code).
I think it is not really history obtrusive.
I will create a small subset for preview and
On Wed, 3 Jul 2013, Veres Lajos wrote:
> Around 99% of the typos are in comments and documentations a few of them
> are only in function/variable names (living code).
> I think it is not really history obtrusive.
>
> I will create a small subset for preview and send it for review
case by case
> basis, although some related cases can certainly be dealt with
> together (and it would upset history a bit so there might even be
> opposition to that).
Around 99% of the typos are in comments and documentations a few of them
are only in function/variable names (living
tions?
>
> > I am writing similar tool, that checks more style issues.
> > I could try to integrate that.
> >
> > My idea is run this as pre-commit hook, separate comments from diff, check
> > it with aspell and print
> > misspelings in standard output so use
mit hook, separate comments from diff, check it
> with aspell and print
> misspelings in standard output so user can filter them.
Classic spellchekers are not really efficient for finding typos in program
sources. There are too many false positives.
Anyway can I help somehow?
And if the
On Wed, Jul 03, 2013 at 12:41:42AM +0200, Veres Lajos wrote:
> Hi,
>
> I wrote a small misspell finder/fixer script and when I have a little
> spare time I clean OS projects with it.
> (https://github.com/vlajos/misspell_fixer)
> I ran it on this repository:
> svn://gcc.gnu.org/svn/gcc/trunk
> Th
Hi,
I wrote a small misspell finder/fixer script and when I have a little
spare time I clean OS projects with it.
(https://github.com/vlajos/misspell_fixer)
I ran it on this repository:
svn://gcc.gnu.org/svn/gcc/trunk
The patch is around 800kb.
What is the best way to handle this modifications?
I
On Fri, 15 Jun 2012, Jonathan Wakely wrote:
>> They clause client code taking the address
>>
>> => cause
>>
>>
>> structs adn classes
>> => and
> So fix them, it's a wiki.
I saw these typos were still there, so I just fixed them.
Thanks for the report, Jay.
Gerald
On 15 June 2012 22:58, Jay K wrote:
> I saw it said "ummutable page".
> I'll check again.
You need to be logged in to edit anything on the wiki, but anyone can
create a user and log in.
On 15 June 2012 21:56, Jay K wrote:
>
> They clause client code taking the address
>
> => cause
>
>
>
>
>
>
>
> structs adn classes
> => and
So fix them, it's a wiki.
They clause client code taking the address
=> cause
structs adn classes
=> and
34 matches
Mail list logo
