<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.arm.com/utility/feedstylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>problem</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/21396/problem</link><description> 
i use keil arm rvct 
and have small problem 
RVCT have no #pragma pack(1) 
but when i got program from my friend i didnt see this program and
RVCT didnt say warning about this command - and i have problem 
because this command destroy execute program</description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: problem</title><link>https://community.arm.com/thread/47973?ContentTypeID=1</link><pubDate>Tue, 19 Jun 2007 14:23:41 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:16541571-33b6-4e66-92e4-3037ae76eca5</guid><dc:creator>test test</dc:creator><description>&lt;p&gt;&lt;p&gt;
SUPER&lt;br /&gt;
new version have no this problem :-)))&lt;/p&gt;

&lt;p&gt;
IDE-Version:&lt;br /&gt;
&amp;micro;Vision3 V3.52&lt;br /&gt;
Copyright (c) Keil Elektronik GmbH / Keil Software, Inc. 1995 -
2007&lt;/p&gt;

&lt;p&gt;
Tool Version Numbers:&lt;br /&gt;
Toolchain Path: BIN31\&lt;br /&gt;
C Compiler: Armcc.Exe V3.1.0.903&lt;br /&gt;
Assembler: Armasm.Exe V3.1.0.903&lt;br /&gt;
Linker/Locator: ArmLink.Exe V3.1.0.903&lt;br /&gt;
Librarian: ArmAr.Exe V3.1.0.903&lt;br /&gt;
Hex Converter: FromElf.Exe V3.1.0.903&lt;br /&gt;
CPU DLL: SARM.DLL V3.10&lt;br /&gt;
Dialog DLL: DARMP.DLL V1.17&lt;br /&gt;
Target DLL: BIN\UL2ARM.DLL V1.30&lt;br /&gt;
Dialog DLL: TARMP.DLL V1.17&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem</title><link>https://community.arm.com/thread/155334?ContentTypeID=1</link><pubDate>Tue, 27 Mar 2007 03:30:37 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:d61f2919-3ee0-46f6-9992-cd5faf93362f</guid><dc:creator>Patrick Noonan</dc:creator><description>&lt;p&gt;&lt;p&gt;
I should clarify that an implementation is free to ignore any
pragmas that it doesn&amp;#39;t recognise. It is not &lt;b&gt;required&lt;/b&gt; to issue
a warning.&lt;/p&gt;

&lt;p&gt;
This implementation does issue warnings though for unrecognised
pragmas. &lt;b&gt;#pragma pack(1)&lt;/b&gt; seems to be special though.&lt;/p&gt;

&lt;p&gt;
This might just be an omission from the documentation rather than
a fault with the compiler though. It remains to be seen.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem</title><link>https://community.arm.com/thread/154954?ContentTypeID=1</link><pubDate>Mon, 26 Mar 2007 12:53:59 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:d28279cb-d026-4144-82d2-307bbf51ca76</guid><dc:creator>test test</dc:creator><description>&lt;p&gt;&lt;p&gt;
DEAR Patrick Noonan&lt;br /&gt;
THANK YOU!!!&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem</title><link>https://community.arm.com/thread/154952?ContentTypeID=1</link><pubDate>Mon, 26 Mar 2007 12:49:52 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:83f875fb-6f8b-47b5-abdb-3716297277f3</guid><dc:creator>test test</dc:creator><description>&lt;p&gt;&lt;p&gt;
&amp;quot;As Dan states, the compiler is free to ignore with a warning any
pragmas that it doesn&amp;#39;t understand.&amp;quot;&lt;br /&gt;
sorry Dan states - only IGNORE- but i said what compiler MUST WARNING
ABOUT IT!!!&lt;/p&gt;

&lt;p&gt;
YOUR POST IS SUPER POST :-))))&lt;br /&gt;
THANK YOU !!!!!!&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem</title><link>https://community.arm.com/thread/154475?ContentTypeID=1</link><pubDate>Mon, 26 Mar 2007 03:54:01 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:2cdf1b1d-52c6-4431-8773-5abfa01b7a27</guid><dc:creator>Patrick Noonan</dc:creator><description>&lt;p&gt;&lt;p&gt;
A summary for those who don&amp;#39;t want to wade through 22 posts to
figure out what the issue here is!!&lt;/p&gt;

&lt;p&gt;
&lt;i&gt;#pragma pack(1)&lt;/i&gt; is not supported by the RVCT compiler
according to the compiler manual. The correct way to pack a structure
is using the __packed attribute.&lt;/p&gt;

&lt;p&gt;
As Dan states, the compiler is free to ignore &lt;b&gt;with a
warning&lt;/b&gt; any pragmas that it doesn&amp;#39;t understand.&lt;/p&gt;

&lt;p&gt;
However the issue here is &amp;ndash; as I understand the description
&amp;ndash; is that the compiler &lt;b&gt;is&lt;/b&gt; recognising &lt;i&gt;#pragma
pack(1)&lt;/i&gt; as a directive to pack the structure with one byte
alignment.&lt;/p&gt;

&lt;p&gt;
It is not however generating the code that will handle accessing
the structure in an unaligned way like the code generated when the
__packed attribute is used.&lt;/p&gt;

&lt;p&gt;
If this is true, then Keil support should have a look at this and
maybe update the compiler manual or remove this #pragma from the
compiler.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem</title><link>https://community.arm.com/thread/155332?ContentTypeID=1</link><pubDate>Sat, 24 Mar 2007 17:49:34 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:b6a1f675-30f0-4dcb-a221-cea36c349f84</guid><dc:creator>Dan Henry</dc:creator><description>&lt;p&gt;&lt;p&gt;
&lt;i&gt;&amp;quot;i finished this topic&lt;br /&gt;
good bye &lt;b&gt;baby&lt;/b&gt;&amp;quot;&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
It is quite unusual to use such terms of endearment in a technical
forum, but in case it is the custom where you are from:&lt;/p&gt;

&lt;p&gt;
Good-bye dear.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem</title><link>https://community.arm.com/thread/154953?ContentTypeID=1</link><pubDate>Sat, 24 Mar 2007 15:24:34 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:4ae80112-1a99-423a-bbb9-56a9a8f11d37</guid><dc:creator>test test</dc:creator><description>&lt;p&gt;&lt;p&gt;
&amp;quot;Ah, very good. That wasn&amp;#39;t too hard, was it? You have finally
shown what the problem is.&lt;/p&gt;

&lt;p&gt;
For whatever ARM you are using or simulating, read up on how it
handles unaligned memory accesses &amp;quot;&lt;/p&gt;

&lt;p&gt;
are you top manager?&lt;br /&gt;
who may see - will be see&lt;/p&gt;

&lt;p&gt;
i finished this topic&lt;br /&gt;
good bye baby ;-)&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem</title><link>https://community.arm.com/thread/154477?ContentTypeID=1</link><pubDate>Sat, 24 Mar 2007 10:41:34 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:afd29091-d281-48ab-8ebf-7f913af62294</guid><dc:creator>Dan Henry</dc:creator><description>&lt;p&gt;&lt;p&gt;
&lt;i&gt;&amp;quot;look at IMPORTANT 17 OPERATOR 17: cmd2.packets =
1000;&amp;quot;&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
Ah, very good. That wasn&amp;#39;t too hard, was it? You have finally
shown what the problem is.&lt;/p&gt;

&lt;p&gt;
For whatever ARM you are using or simulating, read up on how it
handles unaligned memory accesses.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem</title><link>https://community.arm.com/thread/153935?ContentTypeID=1</link><pubDate>Sat, 24 Mar 2007 03:11:28 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:559af359-297a-4406-9931-41f9b863d1cc</guid><dc:creator>test test</dc:creator><description>&lt;p&gt;&lt;p&gt;
if you have no LICENSE - example for evalution version&lt;/p&gt;

&lt;p&gt;
IDE-Version:&lt;br /&gt;
&amp;micro;Vision3 V3.50&lt;br /&gt;
Copyright (c) Keil Elektronik GmbH / Keil Software, Inc. 1995 -
2007&lt;/p&gt;

&lt;p&gt;
Tool Version Numbers:&lt;br /&gt;
Toolchain Path: BIN30\&lt;br /&gt;
C Compiler: ARM/Thumb C/C++ Compiler, RVCT3.0 [Build 951] for uVision
[Evaluation]&lt;br /&gt;
Assembler: ARM/Thumb Macro Assembler, RVCT3.0 [Build 951] for uVision
[Evaluation]&lt;br /&gt;
Linker/Locator: ARM Linker, RVCT3.0 [Build 951] for uVision
[Evaluation]&lt;br /&gt;
Librarian: ARM Archiver, RVCT3.0 [Build 951] for uVision&lt;br /&gt;
Hex Converter: ARM FromELF, RVCT3.0 [Build 951] for uVision
[Evaluation]&lt;br /&gt;
CPU DLL: SARM.DLL V3.04&lt;br /&gt;
Dialog DLL: DARMP.DLL V1.13&lt;br /&gt;
Target DLL: BIN\UL2ARM.DLL V1.26&lt;br /&gt;
Dialog DLL: TARMP.DLL V1.11f&lt;/p&gt;

&lt;pre&gt;
#pragma pack(1)
    12: {
    13:         COMMAND2 cmd2;
    14:         volatile unsigned long Size;
    15:
0x000001B0  E24DD008  SUB       R13,R13,#0x00000008
    16:         cmd2.command = 0x01;
0x000001B4  E3A00001  MOV       R0,#0x00000001
0x000001B8  E5CD0000  STRB      R0,[R13]
    17:         cmd2.packets = 1000;
0x000001BC  E3A00FFA  MOV       R0,#0x000003E8
0x000001C0  E28DC001  ADD       R12,R13,#0x00000001
0x000001C4  E58C0000  STR       R0,[R12]
    18:         Size = cmd2.packets;
0x000001C8  E28DC001  ADD       R12,R13,#0x00000001
0x000001CC  E59C1000  LDR       R1,[R12]
    19:         Size = cmd2.command;
    20:
    21:
0x000001D0  E5DD1000  LDRB      R1,[R13]
    22: }
&lt;/pre&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem</title><link>https://community.arm.com/thread/153310?ContentTypeID=1</link><pubDate>Sat, 24 Mar 2007 02:41:18 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:14ee5798-7529-4a11-8c2a-957ad9e38917</guid><dc:creator>test test</dc:creator><description>&lt;p&gt;&lt;p&gt;
if you want - you may add volatile for clear code&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem</title><link>https://community.arm.com/thread/153937?ContentTypeID=1</link><pubDate>Sat, 24 Mar 2007 02:29:39 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:0b8c1d0b-e1a7-4e11-90d2-1122475ad2fa</guid><dc:creator>test test</dc:creator><description>&lt;p&gt;&lt;p&gt;
****************************************************&lt;br /&gt;
IDE-Version:&lt;br /&gt;
&amp;micro;Vision3 V3.50&lt;br /&gt;
Copyright (c) Keil Elektronik GmbH / Keil Software, Inc. 1995 -
2007&lt;/p&gt;

&lt;p&gt;
Tool Version Numbers:&lt;br /&gt;
Toolchain Path: BIN30\&lt;br /&gt;
C Compiler: ARM/Thumb C/C++ Compiler, RVCT3.0 [Build 951] for uVision
[Full]&lt;br /&gt;
Assembler: ARM/Thumb Macro Assembler, RVCT3.0 [Build 951] for uVision
[Full]&lt;br /&gt;
Linker/Locator: ARM Linker, RVCT3.0 [Build 951] for uVision
[Full]&lt;br /&gt;
Librarian: ARM Archiver, RVCT3.0 [Build 951] for uVision&lt;br /&gt;
Hex Converter: ARM FromELF, RVCT3.0 [Build 951] for uVision
[Full]&lt;br /&gt;
CPU DLL: SARM.DLL V3.04&lt;br /&gt;
Dialog DLL: DARMP.DLL V1.13&lt;br /&gt;
Target DLL: BIN\UL2ARM.DLL V1.26&lt;br /&gt;
Dialog DLL: TARMP.DLL V1.11f&lt;br /&gt;
******************************************************&lt;/p&gt;

&lt;p&gt;
would you like?&lt;br /&gt;
please&lt;br /&gt;
look at IMPORTANT 17 OPERATOR 17: cmd2.packets = 1000;&lt;/p&gt;

&lt;p&gt;
****************************************************&lt;/p&gt;

&lt;pre&gt;
#pragma pack(1)
    12: {
    13:         COMMAND2 cmd2;
    14:         unsigned long Size;
    15:
0x000001B0  E24DD008  SUB       R13,R13,#0x00000008
    16:         cmd2.command = 0x01;
0x000001B4  E3A00001  MOV       R0,#0x00000001
0x000001B8  E5CD0000  STRB      R0,[R13]
    17:         cmd2.packets = 1000;
0x000001BC  E3A00FFA  MOV       R0,#0x000003E8
0x000001C0  E28DC001  ADD       R12,R13,#0x00000001
0x000001C4  E58C0000  STR       R0,[R12]
    18:         Size = cmd2.packets;
0x000001C8  E28DC001  ADD       R12,R13,#0x00000001
0x000001CC  E59C1000  LDR       R1,[R12]
    19:         Size = cmd2.command;
    20:
    21:
0x000001D0  E5DD1000  LDRB      R1,[R13]
    22: }
*****************************************************************
if
typedef __packed struct
{
        unsigned char command;
    unsigned long packets;
    unsigned char reserved[3];

} COMMAND2;
    12: {
    13:         COMMAND2 cmd2;
    14:         unsigned long Size;
    15:
0x000001B0  E92D401C  STMDB     R13!,{R2-R4,R14}
    16:         cmd2.command = 0x01;
0x000001B4  E3A00001  MOV       R0,#0x00000001
0x000001B8  E5CD0000  STRB      R0,[R13]
    17:         cmd2.packets = 1000;
0x000001BC  E28D1001  ADD       R1,R13,#0x00000001
0x000001C0  E3A00FFA  MOV       R0,#0x000003E8
0x000001C4  EB00000E  BL        0x00000204
    18:         Size = cmd2.packets;
0x000001C8  E28D0001  ADD       R0,R13,#0x00000001
0x000001CC  EB000004  BL        0x000001E4
0x000001D0  E1A04000  MOV       R4,R0
    19:         Size = cmd2.command;
    20:
    21:
0x000001D4  E5DD4000  LDRB      R4,[R13]
    22: }
************************************************************************
have no #pragma
only for example what must be when compiler will be ignore #pragma

    12: {
    13:         COMMAND2 cmd2;
    14:         unsigned long Size;
    15:
0x000001B0  E24DD00C  SUB       R13,R13,#0x0000000C
    16:         cmd2.command = 0x01;
0x000001B4  E3A00001  MOV       R0,#0x00000001
0x000001B8  E5CD0000  STRB      R0,[R13]
    17:         cmd2.packets = 1000;
0x000001BC  E3A00FFA  MOV       R0,#0x000003E8
0x000001C0  E58D0004  STR       R0,[R13,#0x0004]
    18:         Size = cmd2.packets;
0x000001C4  E59D1004  LDR       R1,[R13,#0x0004]
    19:         Size = cmd2.command;
    20:
    21:
0x000001C8  E5DD1000  LDRB      R1,[R13]
    22: }

&lt;/pre&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem</title><link>https://community.arm.com/thread/153300?ContentTypeID=1</link><pubDate>Fri, 23 Mar 2007 16:29:14 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:5328088e-2886-4505-9523-3b06ffa26e54</guid><dc:creator>Dan Henry</dc:creator><description>&lt;p&gt;&lt;p&gt;
&lt;i&gt;&amp;quot;Have you really verified that &lt;b&gt;you&lt;/b&gt; have a
problem?&amp;quot;&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
Oh, he/she/it most assuredly has a problem -- the refusal to cut
through all of the drivel and obfuscation by simply posting an
assembly listing.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem</title><link>https://community.arm.com/thread/152625?ContentTypeID=1</link><pubDate>Fri, 23 Mar 2007 16:10:58 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:400fba71-144f-4db4-8092-febf8c945b1d</guid><dc:creator>ImPer Westermark</dc:creator><description>&lt;p&gt;&lt;p&gt;
Conclusion: You are either not able to read (or count to four
either) When seeing more than three words, you ignore it and just
calls it &amp;quot;many words&amp;quot;.&lt;/p&gt;

&lt;p&gt;
I don&amp;#39;t have a problem.&lt;/p&gt;

&lt;p&gt;
Have you really verified that &lt;b&gt;you&lt;/b&gt; have a problem?&lt;/p&gt;

&lt;p&gt;
The compiler does not need to generate a single instruction from
your source code, unless you prove to it that you will use the data.
What you see in the emulator may be random noise left in the
processor registers...&lt;/p&gt;

&lt;p&gt;
Unless you can show that the compiler makes an incorrect
conditional jump, or emits incorrect information, you don&amp;#39;t have a
case.&lt;/p&gt;

&lt;p&gt;
You have also not supplied any assembler listings showing
incorrect code being generated.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem</title><link>https://community.arm.com/thread/147999?ContentTypeID=1</link><pubDate>Fri, 23 Mar 2007 14:55:49 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:d53bed27-4912-49dd-b054-dee54e6ef38b</guid><dc:creator>test test</dc:creator><description>&lt;p&gt;&lt;p&gt;
....................&lt;br /&gt;
very many words .....&lt;/p&gt;

&lt;p&gt;
programm has 4(FORE) commands&lt;br /&gt;
you may try or you have no KEIL COMPILER?&lt;br /&gt;
why did you write here if you have no keil arm compiler(RVTC) which i
wrote up?&lt;br /&gt;
i repeat my question - YOU TRY CODE?&lt;br /&gt;
your answer - many many words about may be yes may be no&lt;br /&gt;
but program has 4(FORE) commands !!!&lt;br /&gt;
if you dont use keil arm(RVTC) what do you want ?&lt;br /&gt;
i wrote about my problem for user whith use keil arm compiler ;-)&lt;br /&gt;
again question ;-)&lt;br /&gt;
do you use keil arm compiler ?&lt;br /&gt;
have you problem whith my code?&lt;br /&gt;
have no problem - ok- i be glad for you ;-)&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem</title><link>https://community.arm.com/thread/147327?ContentTypeID=1</link><pubDate>Fri, 23 Mar 2007 14:20:32 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:7611ce93-9379-4d48-8cc3-7981bf8bda11</guid><dc:creator>ImPer Westermark</dc:creator><description>&lt;p&gt;&lt;p&gt;
Note one thing very important:&lt;/p&gt;

&lt;p&gt;
Two compilers can support a specific pragma, but they may define
it to mean something completely different.&lt;/p&gt;

&lt;p&gt;
My question is still: Have you tried to print the variable
Size?&lt;/p&gt;

&lt;p&gt;
Maybe the compiler do support #pragma pack(1) to mean exactly what
you want it to mean, but are ignoring all use of the Size variable,
since you haven&amp;#39;t shown the compiler that you are really going to use
it...&lt;/p&gt;

&lt;p&gt;
We can try and compile your code. However:&lt;/p&gt;

&lt;p&gt;
1) If you are wrong - we just lost time chasing ghosts.&lt;/p&gt;

&lt;p&gt;
2) If you are correct - then we can&amp;#39;t solve your problem
anyway.&lt;/p&gt;

&lt;p&gt;
3) A lot of users (expectedly all?) here already have an installed
Keil compiler. Will the licensed version behave identically to the
free version? What other settings do we need to care about, since you
are only talking about a couple of lines of code - not a complete
project...&lt;/p&gt;

&lt;p&gt;
4) Not all users here are using the same architecture or
processor, so even if we do use Keil compilers, we might not have to
care about this problem because it may not be applicable to our
projects.&lt;/p&gt;

&lt;p&gt;
5) If there really is an error that do affect us, then the correct
solution is that you send a complete project that correctly
reproduces the problem to Keil support.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem</title><link>https://community.arm.com/thread/146053?ContentTypeID=1</link><pubDate>Fri, 23 Mar 2007 13:35:59 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:718df66f-56f3-4487-ab6a-5796b5772dd8</guid><dc:creator>test test</dc:creator><description>&lt;p&gt;&lt;p&gt;
&amp;quot;No, my compiler may be a different version than yours and produce
different code. My compile options may be different than yours and
produce different code.&amp;quot;&lt;br /&gt;
1 if you wanted - you got evalution version from keil&lt;br /&gt;
2 i try on few version compiler rvtc from keil&lt;br /&gt;
3 you say very much words - but dont said word&lt;br /&gt;
4 try and look - and dont say what you lower man - and try faqs
again&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem</title><link>https://community.arm.com/thread/146052?ContentTypeID=1</link><pubDate>Fri, 23 Mar 2007 13:29:48 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:214b0a40-32fc-4af4-9f38-2f43f78555c4</guid><dc:creator>test test</dc:creator><description>&lt;p&gt;&lt;p&gt;
if we have #pragma pack(1) - which must ignore and compiler must
work how have no pragma&lt;br /&gt;
problem is what when write cmd2.packets = 1000;&lt;br /&gt;
this command erase cmd2.command&lt;/p&gt;

&lt;p&gt;
if we have no #pragma - we will see all OK&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem</title><link>https://community.arm.com/thread/144205?ContentTypeID=1</link><pubDate>Fri, 23 Mar 2007 13:14:44 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:7485dd67-f05b-4e26-8cba-fefb8e5074ef</guid><dc:creator>ImPer Westermark</dc:creator><description>&lt;p&gt;&lt;p&gt;
Have you tried to print the variable Size, or have you only tried
to watch it in the emulator?&lt;/p&gt;

&lt;p&gt;
If your code doesn&amp;#39;t use Size for anything, the compiler may
decide that it isn&amp;#39;t important to make the assign.&lt;/p&gt;

&lt;p&gt;
A lot of strange things can happen if a compiler can deduce that a
variable or an assign is never used.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem</title><link>https://community.arm.com/thread/144204?ContentTypeID=1</link><pubDate>Fri, 23 Mar 2007 13:11:31 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:2dabf474-1b07-44a9-9fd1-45f1a4dc87e4</guid><dc:creator>Dan Henry</dc:creator><description>&lt;p&gt;&lt;p&gt;
&lt;i&gt;&amp;quot;you may create and look code in your compiler&lt;br /&gt;
source C is enough&amp;quot;&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
No, my compiler may be a different version than yours and produce
different code. My compile options may be different than yours and
produce different code.&lt;/p&gt;

&lt;p&gt;
&lt;i&gt;&amp;quot;after it we may say something about problem &amp;quot;&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
No we won&amp;#39;t because I&amp;#39;m done with your profound ignorance
regarding how to present a problem for discussion or solution.&lt;/p&gt;

&lt;p&gt;
&lt;a href="http://www.catb.org/~esr/faqs/smart-questions.html"&gt;www.catb.org/.../smart-questions.html&lt;/a&gt;&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem</title><link>https://community.arm.com/thread/141759?ContentTypeID=1</link><pubDate>Fri, 23 Mar 2007 12:48:58 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:a4b6d8da-7e58-4a45-9b43-7e0ef70351f7</guid><dc:creator>test test</dc:creator><description>&lt;p&gt;&lt;p&gt;
&amp;quot;You have not yet posted the crazy code it generated&amp;quot;&lt;br /&gt;
you may create and look code in your compiler&lt;br /&gt;
source C is enough&lt;/p&gt;

&lt;p&gt;
&amp;quot;Your example produces no output and you didn&amp;#39;t explain how you
observed this craziness and arrived at your conclusion, so there&amp;#39;s
nothing to check.&amp;quot;&lt;/p&gt;

&lt;p&gt;
program has 4 operators&lt;br /&gt;
do you undestand this program? :-))))))))))&lt;br /&gt;
debug this programm in keil emulator - and look on variable Size !!!
and you see bug&lt;/p&gt;

&lt;p&gt;
after it you may look assembler code&lt;/p&gt;

&lt;p&gt;
after it we may say something about problem :-) again&lt;/p&gt;

&lt;p&gt;
i all said ;-)&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem</title><link>https://community.arm.com/thread/138391?ContentTypeID=1</link><pubDate>Fri, 23 Mar 2007 12:12:10 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:31d02a9b-9b65-4d1a-ac20-fda6334a95cd</guid><dc:creator>Dan Henry</dc:creator><description>&lt;p&gt;&lt;p&gt;
&lt;i&gt;&amp;quot;its generate crazy code !!!&amp;quot;&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
You have not yet posted the crazy code it generated.&lt;/p&gt;

&lt;p&gt;
&lt;i&gt;&amp;quot;you dot undestand me - because didnt try my small
example&amp;quot;&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
Your example produces no output and you didn&amp;#39;t explain how you
observed this craziness and arrived at your conclusion, so there&amp;#39;s
nothing to check.&lt;/p&gt;

&lt;p&gt;
If you are so absolutely convinced there is a compiler bug, why
are you posting here instead of contacting Keil Support?&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem</title><link>https://community.arm.com/thread/130142?ContentTypeID=1</link><pubDate>Fri, 23 Mar 2007 11:50:23 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:839e99d7-dd8d-426c-b9f4-fbc5ab977ec9</guid><dc:creator>test test</dc:creator><description>&lt;p&gt;&lt;p&gt;
&amp;quot;bla-bla-bla not supported by compiler #2, compiler #2 can
silently ignore the pragma.&amp;quot;&lt;/p&gt;

&lt;p&gt;
KEIL compiler not support bla-bla-bla&lt;br /&gt;
but MOT IGNORE pragma - its generate crazy code !!!&lt;br /&gt;
try my example and after it we may will say about it&lt;br /&gt;
you dot undestand me - because didnt try my small example&lt;br /&gt;
if you try example you will be suprise !!!&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem</title><link>https://community.arm.com/thread/123731?ContentTypeID=1</link><pubDate>Fri, 23 Mar 2007 09:53:02 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:d2dd155c-8cf5-4714-84db-e3eb97b3c4ba</guid><dc:creator>Dan Henry</dc:creator><description>&lt;p&gt;&lt;p&gt;
&lt;i&gt;&amp;quot;if i wrote in program bla-bla-bla - compiler may dont say
warning about bla-bla-bla?&amp;quot;&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
If &amp;quot;bla-bla-bla&amp;quot; is a pragma supported by compiler #1 and not
supported by compiler #2, compiler #2 can silently ignore the pragma.
That&amp;#39;s the way pragmas work as specified by the C standard, something
which you might want to become more familiar with.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem</title><link>https://community.arm.com/thread/112757?ContentTypeID=1</link><pubDate>Fri, 23 Mar 2007 00:26:35 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:58750c1d-f151-4455-8484-ccc5229999c1</guid><dc:creator>test test</dc:creator><description>&lt;p&gt;&lt;p&gt;
ho-h0&lt;br /&gt;
if i wrote in program bla-bla-bla - compiler may dont say warning
about bla-bla-bla?&lt;br /&gt;
and compiler may do what want free? because does not support
bla-bla-bla ;-)&lt;br /&gt;
it is super compiler ;-)&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: problem</title><link>https://community.arm.com/thread/99051?ContentTypeID=1</link><pubDate>Thu, 22 Mar 2007 11:53:05 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:e131aa2d-3ffe-4570-855f-9d8ca8aa4845</guid><dc:creator>Dan Henry</dc:creator><description>&lt;p&gt;&lt;p&gt;
&lt;i&gt;&amp;quot;try example programm with #pragma pack(1)&amp;quot;&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
Does my compiler claim to support this pragma?&lt;/p&gt;

&lt;p&gt;
&lt;i&gt;&amp;quot;and you will get surprise because Size &amp;lt;&amp;gt; 1 !!!&amp;quot;&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
If my compiler does not support the pragma, I would not at all be
surprised with that result.&lt;/p&gt;

&lt;p&gt;
&lt;i&gt;&amp;quot;and you said ignore pragma?&amp;quot;&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
I said that if your compiler does not support that pragma, it is
free to ignore it without producing a diagnostic. That&amp;#39;s the whole
point of pragmas -- to provide nonstandard implementation-specific
features that other compilers are free to ignore.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>