From dieseinfo at free.fr Fri Jun 1 00:17:24 2007 From: dieseinfo at free.fr (dieseinfo@free.fr) Date: Fri Jun 1 00:25:10 2007 Subject: [Icc-mot] Build/Link time In-Reply-To: <465EF7E9.6090904@spotengineering.com> References: <465750DF.5020408@rjlsystems.com><001201c7a174$2ac329a0$1101a8c0@Technicaldesgnxp1b12e69c9632> <465C3CC6.4080007@labxtechnologies.com><002e01c7a207$80a58370$f68afd52@winxp> <465EF7E9.6090904@spotengineering.com> Message-ID: <000c01c7a41c$e7d53e20$37b04152@winxp> Thank you, Gene ! -----Message d'origine----- De?: icc-mot-bounces@imagecraft.com [mailto:icc-mot-bounces@imagecraft.com] De la part de Gene Norris Envoy??: jeudi 31 mai 2007 18:29 ??: Discussion List for ICC08/11/12/16 users. You do NOT need to subscribe toicc-announce if you are a member of this. Objet?: Re: [Icc-mot] Build/Link time Standard (ANSI) 'C' has 5 predefined macros: Note: they cannot be undefined or redefined. printf("%s",__DATE__); printf("%s",__TIME__); printf("%s",__FILE__); printf("%d",__LINE__); printf("%s",(__STDC__)?"This is standard C.":"This is NOT standard C."); Richard has added the following: __IMAGECRAFT__ and others depending on the specific compiler used: _HC12 (For the hc12 compiler) I believe there is also one based on the specific micro processor...but I'm not exactly sure Gene dieseinfo@free.fr wrote: > Following the discussion about date and compile time, I discover here there are 2 symbolic constants __DATE__ and __TIME__, and this > is very important for me too. > > Are there other constants ? For example compiler version ? > I did'n read anything about this. > > Thank you all, > Best regards. > > Joel Petrique > > > _______________________________________________ > Icc-mot mailing list > Icc-mot@imagecraft.com > http://dragonsgate.net/mailman/listinfo/icc-mot > > > -- Gene Norris Chief Engineer SPOT Engineering, Inc. 1261 Campground Road Lancaster, Ohio 43130 740.654.0880 FAX.654.0889 http://www.spotengineering.com/ _______________________________________________ Icc-mot mailing list Icc-mot@imagecraft.com http://dragonsgate.net/mailman/listinfo/icc-mot From j_baraclough at zetnet.co.uk Fri Jun 1 02:19:17 2007 From: j_baraclough at zetnet.co.uk (John Baraclough) Date: Fri Jun 1 02:29:10 2007 Subject: [Icc-mot] Build/Link time In-Reply-To: <465EF7E9.6090904@spotengineering.com> References: <465750DF.5020408@rjlsystems.com> <001201c7a174$2ac329a0$1101a8c0@Technicaldesgnxp1b12e69c9632> <465C3CC6.4080007@labxtechnologies.com> <002e01c7a207$80a58370$f68afd52@winxp> <465EF7E9.6090904@spotengineering.com> Message-ID: Note that in ICCAVR version 7, the __FILE__ macro originally resolved to the full pathname of the file. It has now been changed back to the same behaviour as in version 6 and returns only the filename. I don't know what the position is in ICCMOT. It may be helpful to some users if there could also be a __PATH__ macro as an added bonus. ;-) All the best for now, John At 17:29 31/05/2007, you wrote: >Standard (ANSI) 'C' has 5 predefined macros: >Note: they cannot be undefined or redefined. > > printf("%s",__DATE__); > printf("%s",__TIME__); > printf("%s",__FILE__); > printf("%d",__LINE__); > printf("%s",(__STDC__)?"This is standard C.":"This is NOT standard C."); > >Richard has added the following: >__IMAGECRAFT__ > >and others depending on the specific compiler used: > >_HC12 >(For the hc12 compiler) > >I believe there is also one based on the specific micro >processor...but I'm not exactly sure > >Gene From dieseinfo at free.fr Fri Jun 1 07:00:50 2007 From: dieseinfo at free.fr (dieseinfo@free.fr) Date: Fri Jun 1 07:08:37 2007 Subject: [Icc-mot] Build/Link time In-Reply-To: References: <465750DF.5020408@rjlsystems.com><001201c7a174$2ac329a0$1101a8c0@Technicaldesgnxp1b12e69c9632><465C3CC6.4080007@labxtechnologies.com><002e01c7a207$80a58370$f68afd52@winxp><465EF7E9.6090904@spotengineering.com> Message-ID: <001701c7a455$43b6fe30$37b04152@winxp> I tried ICC12 compiler about __FILE__ : the full path name is included. But __STDC__ is unknown, without problem for me. Anyway I don't need it. Best regards, and "all the best" Joel -----Message d'origine----- De?: icc-mot-bounces@imagecraft.com [mailto:icc-mot-bounces@imagecraft.com] De la part de John Baraclough Envoy??: vendredi 1 juin 2007 11:19 ??: Discussion List for ICC08/11/12/16 users. You do NOT need to subscribe toicc-announce if you are a member of this. Objet?: Re: [Icc-mot] Build/Link time Note that in ICCAVR version 7, the __FILE__ macro originally resolved to the full pathname of the file. It has now been changed back to the same behaviour as in version 6 and returns only the filename. I don't know what the position is in ICCMOT. It may be helpful to some users if there could also be a __PATH__ macro as an added bonus. ;-) All the best for now, John At 17:29 31/05/2007, you wrote: >Standard (ANSI) 'C' has 5 predefined macros: >Note: they cannot be undefined or redefined. > > printf("%s",__DATE__); > printf("%s",__TIME__); > printf("%s",__FILE__); > printf("%d",__LINE__); > printf("%s",(__STDC__)?"This is standard C.":"This is NOT standard C."); > >Richard has added the following: >__IMAGECRAFT__ > >and others depending on the specific compiler used: > >_HC12 >(For the hc12 compiler) > >I believe there is also one based on the specific micro >processor...but I'm not exactly sure > >Gene _______________________________________________ Icc-mot mailing list Icc-mot@imagecraft.com http://dragonsgate.net/mailman/listinfo/icc-mot From barryc at rjlsystems.com Fri Jun 1 07:37:38 2007 From: barryc at rjlsystems.com (Barry Callahan) Date: Fri Jun 1 07:50:36 2007 Subject: ICC and ANSI ( WAS: Re: [Icc-mot] Build/Link time ) In-Reply-To: <001701c7a455$43b6fe30$37b04152@winxp> References: <465750DF.5020408@rjlsystems.com><001201c7a174$2ac329a0$1101a8c0@Technicaldesgnxp1b12e69c9632><465C3CC6.4080007@labxtechnologies.com><002e01c7a207$80a58370$f68afd52@winxp><465EF7E9.6090904@spotengineering.com> <001701c7a455$43b6fe30$37b04152@winxp> Message-ID: <46602F32.6070108@rjlsystems.com> __STDC__ being undefined (or defined as 0) means that the compiler does not conform to the ANSI C Standard. (any revision) Has anyone put together a writeup describing the various ways that ICC differs from C99? (or alternately C90) I think that'd be an interesting read. dieseinfo@free.fr wrote: > I tried ICC12 compiler about __FILE__ : the full path name is included. > But __STDC__ is unknown, without problem for me. Anyway I don't need it. > > Best regards, and "all the best" > Joel > > > -----Message d'origine----- > De : icc-mot-bounces@imagecraft.com [mailto:icc-mot-bounces@imagecraft.com] De la part de John Baraclough > Envoy? : vendredi 1 juin 2007 11:19 > ? : Discussion List for ICC08/11/12/16 users. You do NOT need to subscribe toicc-announce if you are a member of this. > Objet : Re: [Icc-mot] Build/Link time > > Note that in ICCAVR version 7, the __FILE__ macro originally resolved > to the full pathname of the file. It has now been changed back to the > same behaviour as in version 6 and returns only the filename. I don't > know what the position is in ICCMOT. > > It may be helpful to some users if there could also be a __PATH__ > macro as an added bonus. ;-) > > All the best for now, > John > > At 17:29 31/05/2007, you wrote: > >> Standard (ANSI) 'C' has 5 predefined macros: >> Note: they cannot be undefined or redefined. >> >> printf("%s",__DATE__); >> printf("%s",__TIME__); >> printf("%s",__FILE__); >> printf("%d",__LINE__); >> printf("%s",(__STDC__)?"This is standard C.":"This is NOT standard C."); >> >> Richard has added the following: >> __IMAGECRAFT__ >> >> and others depending on the specific compiler used: >> >> _HC12 >> (For the hc12 compiler) >> >> I believe there is also one based on the specific micro >> processor...but I'm not exactly sure >> >> Gene From ekarpicz at freemail.lt Fri Jun 1 11:26:12 2007 From: ekarpicz at freemail.lt (Edward Karpicz) Date: Fri Jun 1 11:36:08 2007 Subject: ICC and ANSI ( WAS: Re: [Icc-mot] Build/Link time ) References: <465750DF.5020408@rjlsystems.com><001201c7a174$2ac329a0$1101a8c0@Technicaldesgnxp1b12e69c9632><465C3CC6.4080007@labxtechnologies.com><002e01c7a207$80a58370$f68afd52@winxp><465EF7E9.6090904@spotengineering.com> <001701c7a455$43b6fe30$37b04152@winxp> <46602F32.6070108@rjlsystems.com> Message-ID: <000801c7a47a$5552e5d0$a300a8c0@REKS> Barry Callahan wrote: __STDC__ being undefined (or defined as 0) means that the compiler does not conform to the ANSI C Standard. (any revision) I see __STDC__ defined in ICC12 V7. V6 had __STDC__ not defined. So V7 preprocessor is more ANCI C than V6. Has anyone put together a writeup describing the various ways that ICC differs from C99? (or alternately C90) For sure it's not C99. ~1/2 of lib functions is missing. No double, no complex, no long long int etc etc. Edward I think that'd be an interesting read. dieseinfo@free.fr wrote: > I tried ICC12 compiler about __FILE__ : the full path name is included. > But __STDC__ is unknown, without problem for me. Anyway I don't need it. > > Best regards, and "all the best" > Joel > > > -----Message d'origine----- > De : icc-mot-bounces@imagecraft.com > [mailto:icc-mot-bounces@imagecraft.com] De la part de John Baraclough > Envoy? : vendredi 1 juin 2007 11:19 > ? : Discussion List for ICC08/11/12/16 users. You do NOT need to subscribe > toicc-announce if you are a member of this. > Objet : Re: [Icc-mot] Build/Link time > > Note that in ICCAVR version 7, the __FILE__ macro originally resolved to > the full pathname of the file. It has now been changed back to the same > behaviour as in version 6 and returns only the filename. I don't know what > the position is in ICCMOT. > > It may be helpful to some users if there could also be a __PATH__ macro as > an added bonus. ;-) > > All the best for now, > John > > At 17:29 31/05/2007, you wrote: > >> Standard (ANSI) 'C' has 5 predefined macros: >> Note: they cannot be undefined or redefined. >> >> printf("%s",__DATE__); >> printf("%s",__TIME__); >> printf("%s",__FILE__); >> printf("%d",__LINE__); >> printf("%s",(__STDC__)?"This is standard C.":"This is NOT standard >> C."); >> >> Richard has added the following: >> __IMAGECRAFT__ >> >> and others depending on the specific compiler used: >> >> _HC12 >> (For the hc12 compiler) >> >> I believe there is also one based on the specific micro processor...but >> I'm not exactly sure >> >> Gene _______________________________________________ Icc-mot mailing list Icc-mot@imagecraft.com http://dragonsgate.net/mailman/listinfo/icc-mot From barryc at rjlsystems.com Fri Jun 1 12:10:34 2007 From: barryc at rjlsystems.com (Barry Callahan) Date: Fri Jun 1 12:23:38 2007 Subject: ICC and ANSI ( WAS: Re: [Icc-mot] Build/Link time ) In-Reply-To: <000801c7a47a$5552e5d0$a300a8c0@REKS> References: <465750DF.5020408@rjlsystems.com><001201c7a174$2ac329a0$1101a8c0@Technicaldesgnxp1b12e69c9632><465C3CC6.4080007@labxtechnologies.com><002e01c7a207$80a58370$f68afd52@winxp><465EF7E9.6090904@spotengineering.com> <001701c7a455$43b6fe30$37b04152@winxp> <46602F32.6070108@rjlsystems.com> <000801c7a47a$5552e5d0$a300a8c0@REKS> Message-ID: <46606F2A.5080905@rjlsystems.com> Edward Karpicz wrote: > Barry Callahan wrote: > Has anyone put together a writeup describing the various ways > that ICC > differs from C99? (or alternately C90) > > For sure it's not C99. ~1/2 of lib functions is missing. No double, no > complex, no long long int etc etc. I managed to dig up a copy of the C99 spec ( hint: do a Google search for "ISO/IEC 9899:1999" ) It's readily apparent that there are a lot of functions specified by the standard that aren't built-in. I've never had a need for doubles or long longs on the HC12 (I use only ICC12) so it didn't occur to me to look at those data types.... From richard-lists at imagecraft.com Fri Jun 1 12:22:23 2007 From: richard-lists at imagecraft.com (Richard) Date: Fri Jun 1 12:32:29 2007 Subject: ICC and ANSI ( WAS: Re: [Icc-mot] Build/Link time ) In-Reply-To: <46602F32.6070108@rjlsystems.com> References: <465750DF.5020408@rjlsystems.com> <001201c7a174$2ac329a0$1101a8c0@Technicaldesgnxp1b12e69c9632> <465C3CC6.4080007@labxtechnologies.com> <002e01c7a207$80a58370$f68afd52@winxp> <465EF7E9.6090904@spotengineering.com> <001701c7a455$43b6fe30$37b04152@winxp> <46602F32.6070108@rjlsystems.com> Message-ID: <200706011932.l51JWRHI012296@dragonsgate2.imagecraft.com> The accepted language is ANSI C86/C89 except for 64 bit double (which we are actually working on right as we speak...). The lib is a subset. No one has ever asked for the missing bessel functions :-) At 07:37 AM 6/1/2007, Barry Callahan wrote: >__STDC__ being undefined (or defined as 0) means that the compiler >does not conform to the ANSI C Standard. (any revision) > >Has anyone put together a writeup describing the various ways that >ICC differs from C99? (or alternately C90) > >I think that'd be an interesting read. > // richard (This email is for mailing lists. To reach me directly, please use richard at imagecraft.com) From richard-lists at imagecraft.com Fri Jun 1 13:22:47 2007 From: richard-lists at imagecraft.com (Richard) Date: Fri Jun 1 13:32:53 2007 Subject: [Icc-mot] Build/Link time In-Reply-To: <001701c7a455$43b6fe30$37b04152@winxp> References: <465750DF.5020408@rjlsystems.com> <001201c7a174$2ac329a0$1101a8c0@Technicaldesgnxp1b12e69c9632> <465C3CC6.4080007@labxtechnologies.com> <002e01c7a207$80a58370$f68afd52@winxp> <465EF7E9.6090904@spotengineering.com> <001701c7a455$43b6fe30$37b04152@winxp> Message-ID: <200706012032.l51KWqrl013099@dragonsgate2.imagecraft.com> The next release of ICC12 V7 will revert to the just the filename for __FILE__ On V7, we switched to a C99 compliant C preprocessor and the change crept in... At 07:00 AM 6/1/2007, dieseinfo@free.fr wrote: >I tried ICC12 compiler about __FILE__ : the full path name is included. >But __STDC__ is unknown, without problem for me. Anyway I don't need it. > >Best regards, and "all the best" >Joel > // richard (This email is for mailing lists. To reach me directly, please use richard at imagecraft.com) From lance at rapidware.com Fri Jun 1 14:17:39 2007 From: lance at rapidware.com (Lance B. Smith) Date: Fri Jun 1 14:27:36 2007 Subject: [Icc-mot] Build/Link time In-Reply-To: <200706012032.l51KWqrl013099@dragonsgate2.imagecraft.com> Message-ID: <200706012127.l51LRZsL014916@dragonsgate2.imagecraft.com> Richard -- Okay, I can't help but ask, if full path name is C99 compliant, then why not stay with it? I suppose the answer is that it takes too much ROM. However does ANSI-C99 allow a compiler switch for full path vs. single file name, or at least not disallow it? My experience with teaching ANSI-C For Embedded Systems a few years ago was that you can do a lot of things that are "compiler implementation specific" and still be compliant. I can see where you could want either full path or just file name. You may want to have an embedded build list that shows which version of a particular file was actually used (in cases where you have more than one file in your libraries with the same name). Best -- Lance ===================== Lance B. Smith, President Rapidware, Inc. 108 East Main Street Milan, MI 48160 734 439 3990 734 439 3975 Fax lance@rapidware.com www.rapidware.com ===================== -----Original Message----- From: icc-mot-bounces@imagecraft.com [mailto:icc-mot-bounces@imagecraft.com] On Behalf Of Richard Sent: Friday, June 01, 2007 4:23 PM To: Discussion List for ICC08/11/12/16 users. You do NOT need to subscribe toicc-announce if you are a member of this.; 'Discussion List for ICC08/11/12/16 users. You do NOT need tosubscribetoicc-announce if you are a member of this.' Subject: RE: [Icc-mot] Build/Link time The next release of ICC12 V7 will revert to the just the filename for __FILE__ On V7, we switched to a C99 compliant C preprocessor and the change crept in... At 07:00 AM 6/1/2007, dieseinfo@free.fr wrote: >I tried ICC12 compiler about __FILE__ : the full path name is included. >But __STDC__ is unknown, without problem for me. Anyway I don't need it. > >Best regards, and "all the best" >Joel > // richard (This email is for mailing lists. To reach me directly, please use richard at imagecraft.com) _______________________________________________ Icc-mot mailing list Icc-mot@imagecraft.com http://dragonsgate.net/mailman/listinfo/icc-mot From dean.bell at flightec.com Fri Jun 1 14:49:32 2007 From: dean.bell at flightec.com (Dean Bell) Date: Fri Jun 1 14:59:37 2007 Subject: [Icc-mot] Build/Link time In-Reply-To: <200706012127.l51LRZsL014916@dragonsgate2.imagecraft.com> References: <200706012032.l51KWqrl013099@dragonsgate2.imagecraft.com> <200706012127.l51LRZsL014916@dragonsgate2.imagecraft.com> Message-ID: <007101c7a496$bddb8b40$1101a8c0@Technicaldesgnxp1b12e69c9632> Hi Lance This may help http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1124.pdf Page 172 of the pdf 6.10.8 Predefined macro names 1 The following macro names151) shall be defined by the implementation: _ _DATE_ _ The date of translation of the preprocessing translation unit: a character string literal of the form "Mmm dd yyyy", where the names of the months are the same as those generated by the asctime function, and the first character of dd is a space character if the value is less than 10. If the date of translation is not available, an implementation-defined valid date shall be supplied. _ _FILE_ _ The presumed name of the current source file (a character string literal).152) _ _LINE_ _ The presumed line number (within the current source file) of the current source line (an integer constant).152) _ _STDC_ _ The integer constant 1, intended to indicate a conforming implementation. _ _STDC_HOSTED_ _ The integer constant 1 if the implementation is a hosted implementation or the integer constant 0 if it is not. _ _STDC_VERSION_ _ The integer constant 199901L.153) _ _TIME_ _ The time of translation of the preprocessing translation unit: a character string literal of the form "hh:mm:ss" as in the time generated by the asctime function. If the time of translation is not available, an implementation-defined valid time shall be supplied. 2 The following macro names are conditionally defined by the implementation: _ _STDC_IEC_559_ _ The integer constant 1, intended to indicate conformance to the specifications in annex F (IEC 60559 floating-point arithmetic). 151) See ??future language directions?? (6.11.9). 152) The presumed source file name and line number can be changed by the #line directive. 153) This macro was not specified in ISO/IEC 9899:1990 and was specified as 199409L in ISO/IEC 9899/AMD1:1995. The intention is that this will remain an integer constant of type long int that is increased with each revision of this International Standard. 160 Language ?6.10.8 Dean. -----Original Message----- From: icc-mot-bounces@imagecraft.com [mailto:icc-mot-bounces@imagecraft.com] On Behalf Of Lance B. Smith Sent: Saturday, 2 June 2007 09:18 To: 'Discussion List for ICC08/11/12/16 users. You do NOT need tosubscribe toicc-announce if you are a member of this.' Subject: RE: [Icc-mot] Build/Link time Richard -- Okay, I can't help but ask, if full path name is C99 compliant, then why not stay with it? I suppose the answer is that it takes too much ROM. However does ANSI-C99 allow a compiler switch for full path vs. single file name, or at least not disallow it? My experience with teaching ANSI-C For Embedded Systems a few years ago was that you can do a lot of things that are "compiler implementation specific" and still be compliant. I can see where you could want either full path or just file name. You may want to have an embedded build list that shows which version of a particular file was actually used (in cases where you have more than one file in your libraries with the same name). Best -- Lance ===================== Lance B. Smith, President Rapidware, Inc. 108 East Main Street Milan, MI 48160 734 439 3990 734 439 3975 Fax lance@rapidware.com www.rapidware.com ===================== -----Original Message----- From: icc-mot-bounces@imagecraft.com [mailto:icc-mot-bounces@imagecraft.com] On Behalf Of Richard Sent: Friday, June 01, 2007 4:23 PM To: Discussion List for ICC08/11/12/16 users. You do NOT need to subscribe toicc-announce if you are a member of this.; 'Discussion List for ICC08/11/12/16 users. You do NOT need tosubscribetoicc-announce if you are a member of this.' Subject: RE: [Icc-mot] Build/Link time The next release of ICC12 V7 will revert to the just the filename for __FILE__ On V7, we switched to a C99 compliant C preprocessor and the change crept in... At 07:00 AM 6/1/2007, dieseinfo@free.fr wrote: >I tried ICC12 compiler about __FILE__ : the full path name is included. >But __STDC__ is unknown, without problem for me. Anyway I don't need it. > >Best regards, and "all the best" >Joel > // richard (This email is for mailing lists. To reach me directly, please use richard at imagecraft.com) _______________________________________________ Icc-mot mailing list Icc-mot@imagecraft.com http://dragonsgate.net/mailman/listinfo/icc-mot _______________________________________________ Icc-mot mailing list Icc-mot@imagecraft.com http://dragonsgate.net/mailman/listinfo/icc-mot From ekarpicz at freemail.lt Sat Jun 2 02:57:40 2007 From: ekarpicz at freemail.lt (Edward Karpicz) Date: Sat Jun 2 03:07:34 2007 Subject: ICC and ANSI ( WAS: Re: [Icc-mot] Build/Link time ) References: <465750DF.5020408@rjlsystems.com><001201c7a174$2ac329a0$1101a8c0@Technicaldesgnxp1b12e69c9632><465C3CC6.4080007@labxtechnologies.com><002e01c7a207$80a58370$f68afd52@winxp><465EF7E9.6090904@spotengineering.com><001701c7a455$43b6fe30$37b04152@winxp><46602F32.6070108@rjlsystems.com> <200706011932.l51JWRHI012296@dragonsgate2.imagecraft.com> Message-ID: <022901c7a4fc$75071220$a300a8c0@REKS> Richard wrote: > The accepted language is ANSI C86/C89 except for 64 bit double (which we > are actually working on right as we speak...). The lib is a Wow. I'm glad you are working on double. > subset. No one has ever asked for the missing bessel functions :-) > AFAIK there are no Bessel functions in C99. You probably wanted to mention erf and gamma functions? OK, these are for advanced users. But there also is bsearch that could help someone optimizing search through the sorted array of say CAN mailboxes. qsort could be used for median filter, maybe. rint or nearbyint from good lib could save tons of cycles rouding to nearest integer instead of adding a half and converting to int. C99 also specifies fma(a,b,c), fused multiply and accumulate. The trick is to not disregard "not needed" bits of product (24bits * 24bits=48bits) and compute much accurate a*b+c, especially when product and addend have different signs. You may not need fma but when you have it you may easily double your precision: http://cch.loria.fr/documentation/IEEE754/numerical_comp_guide/ppc.doc.html Anyway at least one missing standard fucntion means no compliancy to standard, isn't it? Putchar prototype should be int putchar(int); and not int putchar(char); , isn't it? Regards, Edward > At 07:37 AM 6/1/2007, Barry Callahan wrote: >>__STDC__ being undefined (or defined as 0) means that the compiler does >>not conform to the ANSI C Standard. (any revision) >> >>Has anyone put together a writeup describing the various ways that ICC >>differs from C99? (or alternately C90) >> >>I think that'd be an interesting read. >> > > // richard (This email is for mailing lists. To reach me directly, please > use richard at imagecraft.com) > _______________________________________________ > Icc-mot mailing list > Icc-mot@imagecraft.com > http://dragonsgate.net/mailman/listinfo/icc-mot > From barryc at rjlsystems.com Sun Jun 3 06:45:09 2007 From: barryc at rjlsystems.com (Barry Callahan) Date: Sat Jun 2 05:54:26 2007 Subject: [Icc-mot] Build/Link time In-Reply-To: <200706012127.l51LRZsL014916@dragonsgate2.imagecraft.com> References: <200706012127.l51LRZsL014916@dragonsgate2.imagecraft.com> Message-ID: <4662C5E5.8040002@rjlsystems.com> Lance B. Smith wrote: > Richard -- > Okay, I can't help but ask, if full path name is C99 compliant, then why not > stay with it? I suppose the answer is that it takes too much ROM. However > does ANSI-C99 allow a compiler switch for full path vs. single file name, or > at least not disallow it? C99 doesn't actually specify either behavior. Microsoft's Visual C++ compiler allows you to control this behavior by defining a flag in the build options. From peter at sensair.com Sat Jun 2 05:46:46 2007 From: peter at sensair.com (Peter Lissenburg) Date: Sat Jun 2 06:02:33 2007 Subject: [Icc-mot] 12xDp512 headers In-Reply-To: <022901c7a4fc$75071220$a300a8c0@REKS> References: <465750DF.5020408@rjlsystems.com><001201c7a174$2ac329a0$1101a8c0@Technicaldesgnxp1b12e69c9632><465C3CC6.4080007@labxtechnologies.com><002e01c7a207$80a58370$f68afd52@winxp><465EF7E9.6090904@spotengineering.com><001701c7a455$43b6fe30$37b04152@winxp><46602F32.6070108@rjlsystems.com> <200706011932.l51JWRHI012296@dragonsgate2.imagecraft.com> <022901c7a4fc$75071220$a300a8c0@REKS> Message-ID: <466166B6.3080800@sensair.com> Hi all, I'm working on my first application using the 12xDP512. Tried using the mc9s12dp512.h file, but of course this is not going to work. (I should have looked before I leaped!) So is there a mc9s12xdp512.h file? Or should I start typing? Maybe I have missed something obvious? Thanks for your comments. Peter L. From ekarpicz at freemail.lt Sat Jun 2 06:16:28 2007 From: ekarpicz at freemail.lt (Edward Karpicz) Date: Sat Jun 2 06:26:23 2007 Subject: [Icc-mot] 12xDp512 headers References: <465750DF.5020408@rjlsystems.com><001201c7a174$2ac329a0$1101a8c0@Technicaldesgnxp1b12e69c9632><465C3CC6.4080007@labxtechnologies.com><002e01c7a207$80a58370$f68afd52@winxp><465EF7E9.6090904@spotengineering.com><001701c7a455$43b6fe30$37b04152@winxp><46602F32.6070108@rjlsystems.com> <200706011932.l51JWRHI012296@dragonsgate2.imagecraft.com><022901c7a4fc$75071220$a300a8c0@REKS> <466166B6.3080800@sensair.com> Message-ID: <002c01c7a518$3ac5ace0$a300a8c0@REKS> I just sent my mc9s12xdt512.h to Peter offlist. If others do want I may try to sent it as attachment or text include here? ~40k. Edward ----- Original Message ----- From: "Peter Lissenburg" To: Sent: Saturday, June 02, 2007 15:46 Subject: [Icc-mot] 12xDp512 headers > Hi all, > I'm working on my first application using the 12xDP512. > Tried using the mc9s12dp512.h file, but of course this is not going to > work. (I should have looked before I leaped!) > So is there a mc9s12xdp512.h file? Or should I start typing? > Maybe I have missed something obvious? > Thanks for your comments. > Peter L. > > _______________________________________________ > Icc-mot mailing list > Icc-mot@imagecraft.com > http://dragonsgate.net/mailman/listinfo/icc-mot > From lance at rapidware.com Sat Jun 2 07:26:09 2007 From: lance at rapidware.com (Lance B. Smith) Date: Sat Jun 2 07:36:05 2007 Subject: [Icc-mot] Build/Link time In-Reply-To: <4662C5E5.8040002@rjlsystems.com> Message-ID: <200706021436.l52Ea3eX026702@dragonsgate2.imagecraft.com> Yes, that is what I was suggesting. Thanks for putting it in fewer words ;-) -- Lance -----Original Message----- From: icc-mot-bounces@imagecraft.com [mailto:icc-mot-bounces@imagecraft.com] On Behalf Of Barry Callahan Sent: Sunday, June 03, 2007 9:45 AM To: Discussion List for ICC08/11/12/16 users. You do NOT need to subscribe toicc-announce if you are a member of this. Subject: Re: [Icc-mot] Build/Link time Lance B. Smith wrote: > Richard -- > Okay, I can't help but ask, if full path name is C99 compliant, then why not > stay with it? I suppose the answer is that it takes too much ROM. However > does ANSI-C99 allow a compiler switch for full path vs. single file name, or > at least not disallow it? C99 doesn't actually specify either behavior. Microsoft's Visual C++ compiler allows you to control this behavior by defining a flag in the build options. _______________________________________________ Icc-mot mailing list Icc-mot@imagecraft.com http://dragonsgate.net/mailman/listinfo/icc-mot From barryc at rjlsystems.com Sat Jun 2 15:09:55 2007 From: barryc at rjlsystems.com (Barry Callahan) Date: Sat Jun 2 15:19:46 2007 Subject: [Icc-mot] 12xDp512 headers In-Reply-To: <002c01c7a518$3ac5ace0$a300a8c0@REKS> References: <465750DF.5020408@rjlsystems.com><001201c7a174$2ac329a0$1101a8c0@Technicaldesgnxp1b12e69c9632><465C3CC6.4080007@labxtechnologies.com><002e01c7a207$80a58370$f68afd52@winxp><465EF7E9.6090904@spotengineering.com><001701c7a455$43b6fe30$37b04152@winxp><46602F32.6070108@rjlsystems.com> <200706011932.l51JWRHI012296@dragonsgate2.imagecraft.com><022901c7a4fc$75071220$a300a8c0@REKS> <466166B6.3080800@sensair.com> <002c01c7a518$3ac5ace0$a300a8c0@REKS> Message-ID: <4661EAB3.40400@rjlsystems.com> I seem to recall mention of setting up an area on the imagecraft website for code samples and the like. Send it to Richard to get it posted on the website as a code sample? Edward Karpicz wrote: > I just sent my mc9s12xdt512.h to Peter offlist. If others do want I > may try to sent it as attachment or text include here? ~40k. > > Edward > > ----- Original Message ----- From: "Peter Lissenburg" > To: > Sent: Saturday, June 02, 2007 15:46 > Subject: [Icc-mot] 12xDp512 headers > > >> Hi all, >> I'm working on my first application using the 12xDP512. >> Tried using the mc9s12dp512.h file, but of course this is not going >> to work. (I should have looked before I leaped!) >> So is there a mc9s12xdp512.h file? Or should I start typing? >> Maybe I have missed something obvious? >> Thanks for your comments. >> Peter L. >> >> _______________________________________________ >> Icc-mot mailing list >> Icc-mot@imagecraft.com >> http://dragonsgate.net/mailman/listinfo/icc-mot >> > > > _______________________________________________ > Icc-mot mailing list > Icc-mot@imagecraft.com > http://dragonsgate.net/mailman/listinfo/icc-mot From peter at sensair.com Sat Jun 2 18:03:12 2007 From: peter at sensair.com (Peter Lissenburg) Date: Sat Jun 2 18:18:59 2007 Subject: [Icc-mot] 12xDp512 headers In-Reply-To: <002c01c7a518$3ac5ace0$a300a8c0@REKS> References: <465750DF.5020408@rjlsystems.com><001201c7a174$2ac329a0$1101a8c0@Technicaldesgnxp1b12e69c9632><465C3CC6.4080007@labxtechnologies.com><002e01c7a207$80a58370$f68afd52@winxp><465EF7E9.6090904@spotengineering.com><001701c7a455$43b6fe30$37b04152@winxp><46602F32.6070108@rjlsystems.com> <200706011932.l51JWRHI012296@dragonsgate2.imagecraft.com><022901c7a4fc$75071220$a300a8c0@REKS> <466166B6.3080800@sensair.com> <002c01c7a518$3ac5ace0$a300a8c0@REKS> Message-ID: <46621350.2000902@sensair.com> Thanks Edward, will include ASAP. Pete Edward Karpicz wrote: > I just sent my mc9s12xdt512.h to Peter offlist. If others do want I may > try to sent it as attachment or text include here? ~40k. > > Edward > > ----- Original Message ----- From: "Peter Lissenburg" > To: > Sent: Saturday, June 02, 2007 15:46 > Subject: [Icc-mot] 12xDp512 headers > > >> Hi all, >> I'm working on my first application using the 12xDP512. >> Tried using the mc9s12dp512.h file, but of course this is not going to >> work. (I should have looked before I leaped!) >> So is there a mc9s12xdp512.h file? Or should I start typing? >> Maybe I have missed something obvious? >> Thanks for your comments. >> Peter L. >> >> _______________________________________________ >> Icc-mot mailing list >> Icc-mot@imagecraft.com >> http://dragonsgate.net/mailman/listinfo/icc-mot >> > > > _______________________________________________ > Icc-mot mailing list > Icc-mot@imagecraft.com > http://dragonsgate.net/mailman/listinfo/icc-mot > > > From richard-lists at imagecraft.com Sun Jun 3 03:40:23 2007 From: richard-lists at imagecraft.com (Richard) Date: Sun Jun 3 03:50:38 2007 Subject: [Icc-mot] 12xDp512 headers In-Reply-To: <002c01c7a518$3ac5ace0$a300a8c0@REKS> References: <465750DF.5020408@rjlsystems.com> <001201c7a174$2ac329a0$1101a8c0@Technicaldesgnxp1b12e69c9632> <465C3CC6.4080007@labxtechnologies.com> <002e01c7a207$80a58370$f68afd52@winxp> <465EF7E9.6090904@spotengineering.com> <001701c7a455$43b6fe30$37b04152@winxp> <46602F32.6070108@rjlsystems.com> <200706011932.l51JWRHI012296@dragonsgate2.imagecraft.com> <022901c7a4fc$75071220$a300a8c0@REKS> <466166B6.3080800@sensair.com> <002c01c7a518$3ac5ace0$a300a8c0@REKS> Message-ID: <200706031050.l53AobEY037577@dragonsgate2.imagecraft.com> Edward, if you want, send it to me and I will add it to the next release. Thanks! At 06:16 AM 6/2/2007, Edward Karpicz wrote: >I just sent my mc9s12xdt512.h to Peter offlist. If others do want I >may try to sent it as attachment or text include here? ~40k. > >Edward > // richard (This email is for mailing lists. To reach me directly, please use richard at imagecraft.com) From genenorris at spotengineering.com Tue Jun 12 13:30:51 2007 From: genenorris at spotengineering.com (Gene Norris) Date: Tue Jun 12 13:41:11 2007 Subject: [Icc-mot] An HC12 C++ Compiler? Message-ID: <466F027B.40807@spotengineering.com> #if !defined(__cplusplus) #error C++ compiler required. #endif It may just be the preprocessor? -- Gene Norris Chief Engineer SPOT Engineering, Inc. 1261 Campground Road Lancaster, Ohio 43130 740.654.0880 FAX.654.0889 http://www.spotengineering.com/ From MichaelKern at online.de Wed Jun 13 11:44:35 2007 From: MichaelKern at online.de (Michael Kern) Date: Wed Jun 13 12:51:37 2007 Subject: [Icc-mot] AW: Icc-mot Digest, Vol 34, Issue 4 In-Reply-To: <200706131944.l5DJiQnx093552@dragonsgate2.imagecraft.com> Message-ID: MfG Michael Kern mktw-elektronik GmbH & Co.KG Am Siegenstein 6 57080 Siegen Tel. 0179 1316919 Fax. 0271 2508607 mail. m.kern@mktw-elektronik.de -----Ursprungliche Nachricht----- Von: icc-mot-bounces@imagecraft.com [mailto:icc-mot-bounces@imagecraft.com]Im Auftrag von icc-mot-request@imagecraft.com Gesendet: Mittwoch, 13. Juni 2007 21:45 An: icc-mot@imagecraft.com Betreff: Icc-mot Digest, Vol 34, Issue 4 Send Icc-mot mailing list submissions to icc-mot@imagecraft.com To subscribe or unsubscribe via the World Wide Web, visit http://dragonsgate.net/mailman/listinfo/icc-mot or, via email, send a message with subject or body 'help' to icc-mot-request@imagecraft.com You can reach the person managing the list at icc-mot-owner@imagecraft.com When replying, please edit your Subject line so it is more specific than "Re: Contents of Icc-mot digest..." Today's Topics: 1. An HC12 C++ Compiler? (Gene Norris) ---------------------------------------------------------------------- Message: 1 Date: Tue, 12 Jun 2007 16:30:51 -0400 From: Gene Norris Subject: [Icc-mot] An HC12 C++ Compiler? To: icc-mot@imagecraft.com Message-ID: <466F027B.40807@spotengineering.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed #if !defined(__cplusplus) #error C++ compiler required. #endif It may just be the preprocessor? -- Gene Norris Chief Engineer SPOT Engineering, Inc. 1261 Campground Road Lancaster, Ohio 43130 740.654.0880 FAX.654.0889 http://www.spotengineering.com/ ------------------------------ _______________________________________________ Icc-mot mailing list Icc-mot@imagecraft.com http://dragonsgate.net/mailman/listinfo/icc-mot End of Icc-mot Digest, Vol 34, Issue 4 ************************************** From rbirac at cox.net Thu Jun 28 10:37:33 2007 From: rbirac at cox.net (Alex Brown) Date: Thu Jun 28 10:48:09 2007 Subject: [Icc-mot] Vista compatibility Message-ID: <00cd01c7b9ab$02b5e610$6401a8c0@ddt2> Hi, Can anyone tell me if and how ICC12 (ver 6.14, an oldie but works for me) can be installed to run on Windows Vista? It seemed to install OK, but wouldn't come up. Vista says it looked for a solution to the problem, but didn't report anything. Thanks, Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: http://dragonsgate.net/pipermail/icc-mot/attachments/20070628/c7408e21/attachment.html From richard-lists at imagecraft.com Thu Jun 28 13:29:19 2007 From: richard-lists at imagecraft.com (Richard) Date: Thu Jun 28 13:40:05 2007 Subject: [Icc-mot] Vista compatibility In-Reply-To: <00cd01c7b9ab$02b5e610$6401a8c0@ddt2> References: <00cd01c7b9ab$02b5e610$6401a8c0@ddt2> Message-ID: <200706282040.l5SKe4xd099242@dragonsgate2.imagecraft.com> It's almost certain that the V6 licensing engine has problems with Vista. Not sure why... The latest V7 will need to be rebuilt to be compatible as well. I plan to release a new ICC12 in the next few weeks. At 10:37 AM 6/28/2007, Alex Brown wrote: >Hi, > > Can anyone tell me if and how ICC12 (ver 6.14, an oldie but > works for me) can be installed to run on Windows Vista? It seemed > to install OK, but wouldn't come up. Vista says it looked for a > solution to the problem, but didn't report anything. > >Thanks, >Alex // richard (This email is for mailing lists. To reach me directly, please use richard at imagecraft.com)