Hi Richard,
Today, i verified with android NDK 17 and It is working fine without
disabling compiler optimization.
Thanks,
Sathish
On Mon, May 21, 2018 at 9:41 PM, Sathish Kumar
wrote:
> Thanks, I will do that.
>
> Thanks,
> Sathish
>
>
> On Mon 21 May, 2018, 9:34 PM Richard Hipp, wrote:
>
On Mon, May 21, 2018 at 6:04 PM Richard Hipp wrote:
> > LOCAL_CFLAGS += -O0
> >
> > LOCAL_CPPFLAGS += -O0
> Looks like you have found a bug in clang. I recommend updating to the
> latest version of the compiler that you can get your hands on, and see
> if that doesn't fix the problem.
> Runnin
Thanks, I will do that.
Thanks,
Sathish
On Mon 21 May, 2018, 9:34 PM Richard Hipp, wrote:
> On 5/21/18, Sathish Kumar wrote:
> > Hi Richard,
> > Yes, it works if i disable the compiler optimization. Below is what
> i
> > used in my Android.mk file. Will it create any side effects if we d
On 5/21/18, Sathish Kumar wrote:
> Hi Richard,
> Yes, it works if i disable the compiler optimization. Below is what i
> used in my Android.mk file. Will it create any side effects if we disable
> compiler optimization ?
>
> LOCAL_CFLAGS += -O0
>
> LOCAL_CPPFLAGS += -O0
Looks like you have f
Hi Richard,
Yes, it works if i disable the compiler optimization. Below is what i
used in my Android.mk file. Will it create any side effects if we disable
compiler optimization ?
LOCAL_CFLAGS += -O0
LOCAL_CPPFLAGS += -O0
Thanks,
Sathish
On Fri, May 18, 2018 at 7:28 PM, Sathish Kumar
wro
Ok, I will try.
On Fri 18 May, 2018, 7:15 PM Richard Hipp, wrote:
> On 5/18/18, Sathish Kumar wrote:
> > Hi Richard,
> > Further update on this issue.
> >
> > I am observing this issue only with the library build using ndk-build
> > via terminal and the library built via android studio
On 5/18/18, Sathish Kumar wrote:
> Hi Richard,
> Further update on this issue.
>
> I am observing this issue only with the library build using ndk-build
> via terminal and the library built via android studio gradle works fine. Is
> there any difference in compiling sqlite using gradle and
Hi Richard,
Further update on this issue.
I am observing this issue only with the library build using ndk-build
via terminal and the library built via android studio gradle works fine. Is
there any difference in compiling sqlite using gradle and via ndk-build via
terminal ?
Thanks,
Sathi
Hi Richard,
Is there any issue with this compile option ?
Thanks,
Sathish
On Wed 16 May, 2018, 5:30 PM Sathish Kumar, wrote:
> sqlite> SELECT sqlite_source_id();
>
> 2017-06-08 14:26:16
> 0ee482a1e0eae22e08edc8978c9733a96603d4509645f348ebf55b579e89636b
>
>
> sqlite> PRAGMA compile_optio
sqlite> SELECT sqlite_source_id();
2017-06-08 14:26:16
0ee482a1e0eae22e08edc8978c9733a96603d4509645f348ebf55b579e89636b
sqlite> PRAGMA compile_options;
COMPILER=clang-5.0.300080
DEFAULT_SYNCHRONOUS=2
DEFAULT_WAL_SYNCHRONOUS=2
ENABLE_FTS3
ENABLE_FTS5
ENABLE_JSON1
ENABLE_RTREE
SYSTEM_MALLO
On 05/16/2018 06:20 PM, Sathish Kumar wrote:
Hi,
Sorry, Please find the full sequence below, it is taken from S9 device
running with Android 8.0.
This is a bit strange. The VM code looks correct. Try running a [make
clean] to ensure you're getting a clean build.
If that doesn't work, pleas
On 5/16/18, Sathish Kumar wrote:
> Samsung S9 device with Android 8.0
What output do you see from the following commands:
SELECT sqlite_source_id();
PRAGMA compile_options;
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-u
Samsung S9 device with Android 8.0
On Wed, May 16, 2018 at 4:50 PM, Sathish Kumar
wrote:
> Hi,
> Sorry, Please find the full sequence below, it is taken from S9 device
> running with Android 8.0.
>
> sqlite> create table test (id integer primary key autoincrement, name
> text);
>
> sqlite> inse
Hi,
Sorry, Please find the full sequence below, it is taken from S9 device
running with Android 8.0.
sqlite> create table test (id integer primary key autoincrement, name
text);
sqlite> insert into test (name) values('a');
sqlite> insert into test (name) values('a');
sqlite> insert into test (na
On 5/16/18, Sathish Kumar wrote:
> I just skipped those statements in mail, but i inserted 7 rows.
Please send *exactly* the sequence of commands that you think are
producing an incorrect answer. Please leave nothing to chance, or to
interpretation.
--
D. Richard Hipp
d...@sqlite.org
_
I just skipped those statements in mail, but i inserted 7 rows.
On Wed 16 May, 2018, 4:06 PM Richard Hipp, wrote:
> On 5/16/18, Sathish Kumar wrote:
> > Hi,
> > Please find the below example.
> >
> > sqlite> create table test (id integer primary key autoincrement, name
> > text);
> > sqlite
Hi,
Please find the below example.
sqlite> create table test (id integer primary key autoincrement, name text);
sqlite> insert into test (name) values('a');
sqlite> insert into test (name) values('a');
sqlite> select count(*) from test;
7
sqlite> select * from test limit 10 offset 2;
2|a
3|a
4
On 5/16/18, Sathish Kumar wrote:
> Hi,
> Please find the below example.
>
> sqlite> create table test (id integer primary key autoincrement, name
> text);
> sqlite> insert into test (name) values('a');
> sqlite> insert into test (name) values('a');
> sqlite> select count(*) from test;
> 7
How
On 5/16/18, Sathish Kumar wrote:
> Hi All,
> OFFSET clause is not working as expected in android platform.
>
> [ ISSUE ] : eg. select * from test limit 2 offset 5;
>
> [ Expected Result ] : This query should return two rows starting from index
> 6.
>
> [ Actual Result ] : It always returns ro
Hi All,
OFFSET clause is not working as expected in android platform.
[ ISSUE ] : eg. select * from test limit 2 offset 5;
[ Expected Result ] : This query should return two rows starting from index
6.
[ Actual Result ] : It always returns rows starting from index 2, even
though it had enou
20 matches
Mail list logo