Lucky you ;)
With GCC set to "max. bitchiness" and when compiling individual sources I need
to add the following flags (not all may be currently necessary, but were so in
the past). SQLite still works though :)))
alter= -Wno-cast-qual -Wno-write-strings -Wno-sign-compare
: EXT :[sqlite] Compiler warnings with 3.7.12
I just compiled the the sqlite3 shell from the 3.7.12 amalgamation
download. I got the following warnings:
shell.c:71:0: warning: "popen" redefined [enabled by default]
In file included from shell.c:33:0:
[mingw
path]\bin\../lib/gcc/x86_64-w6
I just compiled the the sqlite3 shell from the 3.7.12 amalgamation
download. I got the following warnings:
shell.c:71:0: warning: "popen" redefined [enabled by default]
In file included from shell.c:33:0:
[mingw
path]\bin\../lib/gcc/x86_64-w64-mingw32/4.7.0/../../../../x86_64-w64-mingw32/include/s
On Thu, Nov 3, 2011 at 2:38 PM, GB wrote:
> When building SQLite for Windows64 using Visual Studio 2010, I get lots of
> warnings concerning 64Bit Values being assigned to 32Bit Variables. These
> occur when the result of pointer arithmetics is assigned to int variables
> since in Windows64 ints
When building SQLite for Windows64 using Visual Studio 2010, I get lots
of warnings concerning 64Bit Values being assigned to 32Bit Variables.
These occur when the result of pointer arithmetics is assigned to int
variables since in Windows64 ints are 32Bits wide while pointers are
64Bit. How ca
On Sat, 19 Feb 2011 10:37:42 -0500, Afriza N. Arief
wrote:
> On Sat, Feb 19, 2011 at 6:27 AM, Samuel Adam wrote:
>
>> A FAQ[2] isn’t enough, as we can see.
>>
>> To put it another way: Bug reporters should have probable cause before
>> they bug others. A compiler warning is only a reasonable
>Date: Fri, 18 Feb 2011 06:13:37 -0800 (PST)
>From: Marian Cascaval
>
>I'm suspecting there's something wrong with Studio Express C++.
>I use both 2008 and 2010 and I notice on 2008 that the IDE loses track of
code
>in case of large source files. Sometimes comments that should have a
certain
>colo
On Sat, Feb 19, 2011 at 6:27 AM, Samuel Adam wrote:
> A FAQ[2] isn’t enough, as we can see.
>
> To put it another way: Bug reporters should have probable cause before
> they bug others. A compiler warning is only a reasonable articulable
> suspicion. Note that “probable cause” doesn’t imply co
>Date: Fri, 18 Feb 2011 13:12:09 +
>From: "Black, Michael (IS)"
>
>I'm of the opinion that all such warnings should be permanently fixed.
Such warnings do point to potential problems.
>And not by disabling the warning but by fixing the code (explicit casts for
example).
>
>How many people try
Just 30 years of developing C code and too-many-to-count projects where we
always had a goal of zero-warnings no matter what switch you used. It's really
hard (as the SQLite guys can attest I'm sure) to make a cross-platform system.
We use each compiler's capabilities as they are all different
On Fri, Feb 18, 2011 at 03:25:46PM +0100, Jean-Denis Muys scratched on the wall:
>
> On 18 f?vr. 2011, at 15:12, Philip Graham Willoughby wrote:
>
> > Adding casts to get rid of warnings is usually the wrong answer in my
> > experience. Certainly you should never cast the return value of a
> > fu
On 18 févr. 2011, at 16:51, Philip Graham Willoughby wrote:
>
>> malloc returns a 64 bit pointer of type void *
>
> No, from the caller's point of view it returns an int if you haven't included
> .
Indeed. I assumed the programmer had included the standard headers. On my
system, any implici
On 18 Feb 2011, at 14:25, Jean-Denis Muys wrote:
> On 18 févr. 2011, at 15:12, Philip Graham Willoughby wrote:
>
>> Adding casts to get rid of warnings is usually the wrong answer in my
>> experience. Certainly you should never cast the return value of a function
>> call because that hides the
On 18 févr. 2011, at 15:12, Philip Graham Willoughby wrote:
> Adding casts to get rid of warnings is usually the wrong answer in my
> experience. Certainly you should never cast the return value of a function
> call because that hides the problems you get when it's implicitly returning
> int b
. Arief
To: General Discussion of SQLite Database
Sent: Thu, February 17, 2011 7:26:33 AM
Subject: [sqlite] Compiler warnings in R-Tree code under Visual Studio Express
Hi,
Microsoft Visual Studio Express C++ is available for free from
http://www.microsoft.com/express/Downloads/#2010-Visual-CPP
I
On 18 Feb 2011, at 13:12, Black, Michael (IS) wrote:
> I'm of the opinion that all such warnings should be permanently fixed. Such
> warnings do point to potential problems.
> And not by disabling the warning but by fixing the code (explicit casts for
> example).
It's been a while since I last
__
> From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on
> behalf of Nick Shaw [nick.s...@citysync.co.uk]
> Sent: Friday, February 18, 2011 3:50 AM
> To: General Discussion of SQLite Database
> Subject: EXT :Re: [sqlite] Compiler wa
_
From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on
behalf of Nick Shaw [nick.s...@citysync.co.uk]
Sent: Friday, February 18, 2011 3:50 AM
To: General Discussion of SQLite Database
Subject: EXT :Re: [sqlite] Compiler warnings in R-Tree code under Visual
StudioExpress
A
Afriza N. Arief wrote:
> I tried to compile SQLite 3.7.5 with SQLITE_ENABLE_RTREE=1 and got the
following warnings:
>
> sqlite3.c(120736): warning C4244: '=' : conversion from 'double' to
'float', possible loss of data
> sqlite3.c(120749): warning C4244: '+=' : conversion from 'double' to
'float',
Hi,
Microsoft Visual Studio Express C++ is available for free from
http://www.microsoft.com/express/Downloads/#2010-Visual-CPP
I tried to compile SQLite 3.7.5 with SQLITE_ENABLE_RTREE=1 and got the
following warnings:
sqlite3.c(120736): warning C4244: '=' : conversion from 'double' to 'float',
p
Hi,
I've integrated the extension-functions.c code into an R package so that
these functions can be used in R via RSQLite. In the process, I came
across a couple of compiler warnings that seemed to have easy fixes. I
could not find contact information for Liam Healy so am posting this here.
Tha
On Nov 17, 2009, at 3:39 PM, r...@lambdares.com wrote:
>
> Hello,
>
> I'm receiving the following compiler warnings with VS2005 for both
> Win32 and x64 platforms.
Harmless.
http://www.sqlite.org/src/vinfo/f1c09acaca3e205acf5b077c9b2d0fe35f035c1e
>
> -- Rich
>
> .\sqlite3.c(49492) : warnin
Hello,
I'm receiving the following compiler warnings with VS2005 for both Win32 and
x64 platforms.
-- Rich
.\sqlite3.c(49492) : warning C4244: 'function' : conversion from 'ynVar' to
'int', possible loss of data
.\sqlite3.c(51336) : warning C4244: 'return' : conversion from 'ynVar' to
'int
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nicolas Williams wrote:
> Oh, I think you meant that the L suffix would break on anything other
> than LP64 or ILP64 models.
Correct. L means long. On platforms where long is 32 bits, shifting a long
value by more than 32 bits will give zero.
> I'm
On Tue, Sep 29, 2009 at 05:28:39PM -0700, Roger Binns wrote:
> Nicolas Williams wrote:
> > On Tue, Sep 29, 2009 at 11:21:30AM -0700, Roger Binns wrote:
> >> Nicolas Williams wrote:
> >>> If you move the cast to the left the warning should go away:
> >>> ((sqlite3_int64)(1L<<63))
> >> And this is w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nicolas Williams wrote:
> On Tue, Sep 29, 2009 at 11:21:30AM -0700, Roger Binns wrote:
>> Nicolas Williams wrote:
>>> If you move the cast to the left the warning should go away:
>>> ((sqlite3_int64)(1L<<63))
>> And this is why making warnings go away
On Tue, Sep 29, 2009 at 12:05:21PM -0700, Jim Showalter wrote:
> Warnings are never harmless--they clutter the build output and
> introduce cognitive dissonance when trying to see if a build is clean
> or not.
>
> I worked on a project where they hadn't enabled warnings during
> development bec
On Tue, Sep 29, 2009 at 11:21:30AM -0700, Roger Binns wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Nicolas Williams wrote:
> > If you move the cast to the left the warning should go away:
> > ((sqlite3_int64)(1L<<63))
>
> And this is why making warnings go away leads to bugs. Th
t: Tuesday, September 29, 2009 3:38 AM
Subject: Re: [sqlite] Compiler warnings with Sun Studio 12.1 on
Solaris 10
>
> On Sep 27, 2009, at 5:28 PM, Dr. David Kirkby wrote:
>
>> "sqlite3.c", line 18731: warning: integer overflow detected: op
>> "<<&quo
On Sep 29, 2009, at 2:21 PM, Roger Binns wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Nicolas Williams wrote:
>> If you move the cast to the left the warning should go away:
>> ((sqlite3_int64)(1L<<63))
>
> And this is why making warnings go away leads to bugs. The
> replacem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nicolas Williams wrote:
> If you move the cast to the left the warning should go away:
> ((sqlite3_int64)(1L<<63))
And this is why making warnings go away leads to bugs. The replacement
above will only work if sizeof(long)==sizeof(long long) which i
On Tue, Sep 29, 2009 at 06:38:44AM -0400, D. Richard Hipp wrote:
>
> On Sep 27, 2009, at 5:28 PM, Dr. David Kirkby wrote:
>
> > "sqlite3.c", line 18731: warning: integer overflow detected: op "<<"
> > "sqlite3.c", line 18748: warning: integer overflow detected: op "<<"
>
> Both cases are complai
On Sep 27, 2009, at 5:28 PM, Dr. David Kirkby wrote:
> "sqlite3.c", line 18731: warning: integer overflow detected: op "<<"
> "sqlite3.c", line 18748: warning: integer overflow detected: op "<<"
Both cases are complaining about a constant: (0x1f<<28)Both are
harmless.
> "sqlite3.c", line
D. Richard Hipp wrote:
>> Thank you.
>>
>> I understand you can't fix these warnings since you don't have
>> access to
>> such machines. Would you like access? If so, I can give you access
>> to a
>> 16-core Sun T5240 at the university of Washington, with runs Solaris
>> 10
>> update 7 (lates
On Sep 28, 2009, at 10:15 AM, Dr. David Kirkby wrote:
> Roger Binns wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Dr. David Kirkby wrote:
>>> "sqlite3.c", line 18731: warning: integer overflow detected: op "<<"
>>> "sqlite3.c", line 18748: warning: integer overflow detected: op
Roger Binns wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Dr. David Kirkby wrote:
>> "sqlite3.c", line 18731: warning: integer overflow detected: op "<<"
>> "sqlite3.c", line 18748: warning: integer overflow detected: op "<<"
>> "sqlite3.c", line 32546: warning: statement not reache
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dr. David Kirkby wrote:
> "sqlite3.c", line 18731: warning: integer overflow detected: op "<<"
> "sqlite3.c", line 18748: warning: integer overflow detected: op "<<"
> "sqlite3.c", line 32546: warning: statement not reached
> "sqlite3.c", line 69160: w
"sqlite3.c", line 18731: warning: integer overflow detected: op "<<"
"sqlite3.c", line 18748: warning: integer overflow detected: op "<<"
"sqlite3.c", line 32546: warning: statement not reached
"sqlite3.c", line 69160: warning: integer overflow detected: op "<<"
send in a patch ;)
On Fri, 5 Nov 2004 08:33:51 -0600, Stober, Mel <[EMAIL PROTECTED]> wrote:
> When I compile the 3.0.8 source with VC++ 6.0 (SP5 installed) compiler as a
> DLL, the compiler spews out 131 warnings about type mismatch, integral size
> mismatch, conversion from '__int64 ' to 'int,
When I compile the 3.0.8 source with VC++ 6.0 (SP5 installed) compiler as a
DLL, the compiler spews out 131 warnings about type mismatch, integral size
mismatch, conversion from '__int64 ' to 'int, and a host of other
miscellaneous warnings.
Any thoughts about the SQLite project programmers cleani
Hi!
When compiled (with VC++) SQLite produces about 350 and more compiler (level 3/4)
warnings. Is there any effort in progress to reduce / eliminate these warnings, is
there a possibility to contribute to lower the number of warnings, or doesn't simply
care anyone about *grin* ??
Greetings, R
41 matches
Mail list logo
