• State Not Answered
  • Locked Locked
  • Replies 27 replies
  • Subscribers 22 subscribers
  • Views 4341 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Multiple call to segment warning

Donghua Gu

I am seeing this warning when I try to compile my code

Warning L15: multiple call to segment
segment: ?pr?_nvmwrit?nvmem_cc
caller1: ?pr?spicommisr?spi_com_cc
caller2: ?c_c51startup

I looked through my code, I don't call nvmwrite in spicommisr routine. And what is this c51startup file?

thanks,
DG

Parents
  • 0 in reply to erik malund

    if you insist that "C is C" I suggest you get yourself a PC to program.

    Too a harsh a judgment I think. A couple of years ago I was involved in the development of, what I still consider, the most beautiful piece of time critical C (and some C++) code I ever saw, which was written mostly in standard C/C++. Things were not taken to extremes to squeeze the processors (XC167CI), but that did not reduce the code's functional value and did not change the fact the it bread an entire generation of successful machines. I doubt whether the people that were/still are involved in that effort would appreciate your job offer :-)

Reply
  • 0 in reply to erik malund

    if you insist that "C is C" I suggest you get yourself a PC to program.

    Too a harsh a judgment I think. A couple of years ago I was involved in the development of, what I still consider, the most beautiful piece of time critical C (and some C++) code I ever saw, which was written mostly in standard C/C++. Things were not taken to extremes to squeeze the processors (XC167CI), but that did not reduce the code's functional value and did not change the fact the it bread an entire generation of successful machines. I doubt whether the people that were/still are involved in that effort would appreciate your job offer :-)

Children
  • 0 in reply to Catcus Blip

    Things were not taken to extremes to squeeze the processors
    no such intent in my post, if you do not need to, then why try?
    However, there are some things where considering the achitectural facts and the compiler circumvention thereof get important.
    Basically what I comment on is the udder (yes it i bovine) refusal of some to adapt to what they are working with, namely Keil C51, not just "some C"

    Erik