Anonymous | Login | Signup for a new account | 2025-02-09 10:40 UTC | ![]() |
Main | My View | View Issues | Change Log | Roadmap |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
0000699 | Taste | [All Projects] General | public | 2017-10-26 14:09 | 2018-01-23 15:41 | ||||||
Reporter | miguel_munoz | ||||||||||
Assigned To | maxime | ||||||||||
Priority | normal | Severity | minor | Reproducibility | have not tried | ||||||
Status | assigned | Resolution | open | ||||||||
Platform | All | OS | OS Version | ||||||||
Summary | 0000699: Native encoding not checked between nodes of different architecture | ||||||||||
Description | The editors and code generation allow that an interface with parameters set to native encoding is deployed between nodes that have a different architecture (e.g. x86 and leon). The information contained in the models should be sufficient to detect this condition, and report an error. Otherwise, at runtime, this will produce garbage data or possibly a crash. | ||||||||||
Tags | No tags attached. | ||||||||||
Attached Files | |||||||||||
![]() |
|
(0003063) ttsiodras (administrator) 2017-10-26 14:50 |
Indeed, this should be handled. Maxime, can the check be done in buildsupport? |
(0003206) maxime (administrator) 2018-01-23 15:41 |
I propose an alternative : we should rename "Native" to "Automatic" and let the tools make sure the encoding ensures consistent data. On local nodes, Native will be chosen, and whenever there is distribution across networks, uPER would be chosen. |
![]() |
|||
Date Modified | Username | Field | Change |
2017-10-26 14:09 | miguel_munoz | New Issue | |
2017-10-26 14:49 | ttsiodras | Assigned To |
=> maxime |
2017-10-26 14:49 | ttsiodras | Status |
new => assigned |
2017-10-26 14:50 | ttsiodras | Note Added: 0003063 | |
2018-01-23 15:41 | maxime | Note Added: 0003206 |
Copyright © 2000 - 2011 MantisBT Group |