public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-bugs@ecos.sourceware.org
Subject: [Bug 1002008] New: using floating-point operations
Date: Wed, 03 Sep 2014 13:36:00 -0000 [thread overview]
Message-ID: <bug-1002008-13@http.bugs.ecos.sourceware.org/> (raw)
Please do not reply to this email, use the link below.
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1002008
Bug ID: 1002008
Summary: using floating-point operations
Product: eCos
Version: 3.0
Target: All
Architecture/Host ARM
OS:
Status: UNCONFIRMED
Severity: critical
Priority: low
Component: Other
Assignee: unassigned@bugs.ecos.sourceware.org
Reporter: akinin_a@oaoesp.ru
CC: ecos-bugs@ecos.sourceware.org
Created attachment 2540
--> http://bugs.ecos.sourceware.org/attachment.cgi?id=2540&action=edit
Most of the program code and the description in the application. (pdf file)
Hello. We had a problem when programming in our controller.
That we have:
1. LPC3210, ARM-9, eCos 3.0
2. thread - "Main cycle"
cyg_thread_create (
PRI_MAIN_CYCLE,// priority
MainCycle, // entry
0, // entry parameter
"Main cycle", // name
&thread_stack[MAIN_THREAD], // stack
STACK_SIZE, // stack size
&handle[MAIN_THREAD], // handle
&thread_data[MAIN_THREAD]); // thread data structure
3. Interrupt ADC ( 1 per 200 microseconds)
4. Two different cycle on thred “Main cycle"
int it;
float mtest_element[101];
int mtest_intelement[101];
long long mtest_longelement[101];
part code 1:
mtest_longelement[it]=(long long)mtest_element[it];
if(mtest_longelement[it]!=(long long)it)
{
diag_printf("ERROR err_i %d int %d \n", mtest_longelement[it], it);
}
part code 2:
mtest_intelement[it]=(int)mtest_element[it];
if(mtest_intelement[it]!=it)
{
diag_printf("ERROR err_i %d int %d \n", mtest_intelement[it], it);
}
Case 1
When we use an array of "long long" type and ADC interrupt is enabled all is
OK.
Case 2
When we use an array of "int" type and ADC interrupt is enabled there is data
corruption.
Case 3
When we use an array of "int" type and ADC interrupt is disabled all is OK too.
What wrong?
We certainly observe that the interrupt handler working with VFP modifies float
data used in other thread. How and where is the VFP state saving realized?
Most of the program code in the attachment.
Thank you,
Andrey.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From ecos-bugs-return-10877-listarch-ecos-bugs=sources.redhat.com@sourceware.org Wed Sep 03 13:36:31 2014
Return-Path: <ecos-bugs-return-10877-listarch-ecos-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-ecos-bugs@sources.redhat.com
Received: (qmail 30332 invoked by alias); 3 Sep 2014 13:36:31 -0000
Mailing-List: contact ecos-bugs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <ecos-bugs.sourceware.org>
List-Subscribe: <mailto:ecos-bugs-subscribe@sourceware.org>
List-Post: <mailto:ecos-bugs@sourceware.org>
List-Help: <mailto:ecos-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: ecos-bugs-owner@sourceware.org
Delivered-To: mailing list ecos-bugs@sourceware.org
Received: (qmail 30315 invoked by uid 89); 3 Sep 2014 13:36:30 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-3.0 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mail.ecoscentric.com
Received: from albus.ecoscentric.com (HELO mail.ecoscentric.com) (212.13.207.200)
by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Wed, 03 Sep 2014 13:36:28 +0000
Received: by mail.ecoscentric.com (Postfix, from userid 512)
id 505F5A88A68; Wed, 3 Sep 2014 14:36:25 +0100 (BST)
X-Original-To: unassigned@bugs.ecos.sourceware.org
Delivered-To: unassigned@bugs.ecos.sourceware.org
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: unassigned@bugs.ecos.sourceware.org
Subject: [Bug 1002008] New: using floating-point operations
Date: Wed, 03 Sep 2014 13:36:00 -0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: eCos
X-Bugzilla-Component: Other
X-Bugzilla-Keywords:
X-Bugzilla-Severity: critical
X-Bugzilla-Who: akinin_a@oaoesp.ru
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: low
X-Bugzilla-Assigned-To: unassigned@bugs.ecos.sourceware.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
op_sys bug_status bug_severity priority component assigned_to reporter cc
Message-ID: <bug-1002008-777@http.bugs.ecos.sourceware.org/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.ecos.sourceware.org/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014/txt/msg00244.txt.bz2
Content-length: 2406
Please do not reply to this email, use the link below.
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1002008
Bug ID: 1002008
Summary: using floating-point operations
Product: eCos
Version: 3.0
Target: All
Architecture/Host ARM
OS:
Status: UNCONFIRMED
Severity: critical
Priority: low
Component: Other
Assignee: unassigned@bugs.ecos.sourceware.org
Reporter: akinin_a@oaoesp.ru
CC: ecos-bugs@ecos.sourceware.org
Created attachment 2540
--> http://bugs.ecos.sourceware.org/attachment.cgi?id=2540&action=edit
Most of the program code and the description in the application. (pdf file)
Hello. We had a problem when programming in our controller.
That we have:
1. LPC3210, ARM-9, eCos 3.0
2. thread - "Main cycle"
cyg_thread_create (
PRI_MAIN_CYCLE,// priority
MainCycle, // entry
0, // entry parameter
"Main cycle", // name
&thread_stack[MAIN_THREAD], // stack
STACK_SIZE, // stack size
&handle[MAIN_THREAD], // handle
&thread_data[MAIN_THREAD]); // thread data structure
3. Interrupt ADC ( 1 per 200 microseconds)
4. Two different cycle on thred “Main cycle"
int it;
float mtest_element[101];
int mtest_intelement[101];
long long mtest_longelement[101];
part code 1:
mtest_longelement[it]=(long long)mtest_element[it];
if(mtest_longelement[it]!=(long long)it)
{
diag_printf("ERROR err_i %d int %d \n", mtest_longelement[it], it);
}
part code 2:
mtest_intelement[it]=(int)mtest_element[it];
if(mtest_intelement[it]!=it)
{
diag_printf("ERROR err_i %d int %d \n", mtest_intelement[it], it);
}
Case 1
When we use an array of "long long" type and ADC interrupt is enabled all is
OK.
Case 2
When we use an array of "int" type and ADC interrupt is enabled there is data
corruption.
Case 3
When we use an array of "int" type and ADC interrupt is disabled all is OK too.
What wrong?
We certainly observe that the interrupt handler working with VFP modifies float
data used in other thread. How and where is the VFP state saving realized?
Most of the program code in the attachment.
Thank you,
Andrey.
--
You are receiving this mail because:
You are the assignee for the bug.
>From ecos-bugs-return-10880-listarch-ecos-bugs=sources.redhat.com@sourceware.org Wed Sep 03 13:41:27 2014
Return-Path: <ecos-bugs-return-10880-listarch-ecos-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-ecos-bugs@sources.redhat.com
Received: (qmail 2025 invoked by alias); 3 Sep 2014 13:41:27 -0000
Mailing-List: contact ecos-bugs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <ecos-bugs.sourceware.org>
List-Subscribe: <mailto:ecos-bugs-subscribe@sourceware.org>
List-Post: <mailto:ecos-bugs@sourceware.org>
List-Help: <mailto:ecos-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: ecos-bugs-owner@sourceware.org
Delivered-To: mailing list ecos-bugs@sourceware.org
Received: (qmail 2001 invoked by uid 89); 3 Sep 2014 13:41:27 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2
X-HELO: mail.ecoscentric.com
Received: from albus.ecoscentric.com (HELO mail.ecoscentric.com) (212.13.207.200)
by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Wed, 03 Sep 2014 13:41:26 +0000
Received: from localhost (localhost [127.0.0.1])
by mail.ecoscentric.com (Postfix) with ESMTP id 88EDEA88AB7
for <ecos-bugs@ecos.sourceware.org>; Wed, 3 Sep 2014 14:41:23 +0100 (BST)
Received: from mail.ecoscentric.com ([127.0.0.1])
by localhost (albus.ecoscentric.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id natTSEH4a0vH; Wed, 3 Sep 2014 14:41:23 +0100 (BST)
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-bugs@ecos.sourceware.org
Subject: [Bug 1002008] using floating-point operations
Date: Wed, 03 Sep 2014 13:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: eCos
X-Bugzilla-Component: Other
X-Bugzilla-Keywords:
X-Bugzilla-Severity: critical
X-Bugzilla-Who: akinin_a@oaoesp.ru
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: low
X-Bugzilla-Assigned-To: unassigned@bugs.ecos.sourceware.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields: rep_platform
Message-ID: <bug-1002008-13-5iGfJZ5uzJ@http.bugs.ecos.sourceware.org/>
In-Reply-To: <bug-1002008-13@http.bugs.ecos.sourceware.org/>
References: <bug-1002008-13@http.bugs.ecos.sourceware.org/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://bugs.ecos.sourceware.org/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014/txt/msg00247.txt.bz2
Content-length: 438
Please do not reply to this email, use the link below.
http://bugs.ecos.sourceware.org/show_bug.cgi?id\x1002008
Andrey <akinin_a@oaoesp.ru> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target|All |Custom (Customer specific)
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2014-09-03 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 13:36 bugzilla-daemon [this message]
2014-09-04 14:35 ` [Bug 1002008] " bugzilla-daemon
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=bug-1002008-13@http.bugs.ecos.sourceware.org/ \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-bugs@ecos.sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).