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

Strange Way to Code

I came accross this code fragment when reviewing some sample code for ethernet. Didnt even try to build it. Would the delay function even be called if no executable code is in the body? I would think it would be optimized out under all circumstances? In my opionion, its not the right way to do it anyway...

Just curious ...

static void delay (void) {;};


/*--------------------------- output_MDIO -----------------------------------*/

static void output_MDIO (U32 val, U32 n) {

   /* Output a value to the MII PHY management interface. */
   for (val <<= (32 - n); n; val <<= 1, n--) {
      if (val & 0x80000000) {
         GPIO2->FIOSET = MDIO;
      }
      else {
         GPIO2->FIOCLR = MDIO;
      }
      delay ();
      GPIO2->FIOSET = MDC;
      delay ();
      GPIO2->FIOCLR = MDC;
   }
}

Parents
  • That's interesting, though: what's a portable way of creating a short delay? Reading a dummy volatile variable, maybe?

    I would personally use 'ASM NOP' or something equivalent to ensure a delay within the processor. A dummy function call is a bad choice for a delay, as it may not get compiled-in in many situations/environments. Additionally, if the delay must be precise, interrupt processing must also have to be accounted for as a possibility. Not to mention task preemption if in an RTOS. Etc..Etc..Etc...

    Just thought this was strange. But, no author on/in the code, so no accountability here...

Reply
  • That's interesting, though: what's a portable way of creating a short delay? Reading a dummy volatile variable, maybe?

    I would personally use 'ASM NOP' or something equivalent to ensure a delay within the processor. A dummy function call is a bad choice for a delay, as it may not get compiled-in in many situations/environments. Additionally, if the delay must be precise, interrupt processing must also have to be accounted for as a possibility. Not to mention task preemption if in an RTOS. Etc..Etc..Etc...

    Just thought this was strange. But, no author on/in the code, so no accountability here...

Children