Skip to content
  1. Jan 11, 2016
  2. Jan 10, 2016
  3. Jan 09, 2016
  4. Jan 08, 2016
  5. Jan 07, 2016
  6. Jan 06, 2016
  7. Jan 05, 2016
    • Gregory Nutt's avatar
      Cosmetic spacing change · b28bf55f
      Gregory Nutt authored
      b28bf55f
    • Gregory Nutt's avatar
      Fix an ommission in compiler.h · 670ac9fb
      Gregory Nutt authored
      670ac9fb
    • Dimitry Kloper's avatar
      Fix 64-bit clock-related constant value evaluation for AVR compiler · 06438b0d
      Dimitry Kloper authored
      This may be specific for Atmel AVR8 toolchain compiler.
      The problem is that despite of being 8-bit architecture
      avr-gcc supports uint64_t, but the following code
      
      uint64_t value = 10000 * 1000;
      
      produces a wrong negative value in the final code (tested
      both with and without optimization).
      
      The work-around is simple:
      
      uint64_t value = 10000 * 1000L;
      
      The code is a reduced part from sched/signal/sig_timedwait.c where
      waitticks64 is calculated using NSEC_PER_TICK. This one is defined
      as USEC_PER_TICK * NSEC_PER_USEC which leads to the example above.
      06438b0d
    • Vladimir Komendantskiy's avatar
    • Dimitry Kloper's avatar
      Introduce support for Atmel toolchain in-flash strings · 06d83c62
      Dimitry Kloper authored
      Atmel toolchain AVR compiler provides a transparent in-flash object support using __flash and __memx symbols. The former indicates to compiler that this is a flash-based object.  The later used with pointer indicates that the referenced object may reside either in flash or in RAM. The compiler automatically makes 32-bit pointer with flag indicating whether referenced object is in flash or RAM and generates code to access either in run-time. Thus, any function that accepts __memx object can transparently work with RAM and flash objects.
      
      For platforms with a Harvard architecture and a very small RAM like AVR this allows to move all constant strings used in trace messages to flash in the instruction address space, releasing resources for other things.
      
      This change introduces IOBJ and IPTR type qualifiers.  The 'I' indicates that the object may like in instruction space on a Harvard architecture machine.
      
      For platforms that do not have __flash and __memx or similar symbols IOBJ and IPTR are empty, making the types equivalent to, for example, 'const char' and 'const char*'.  For Atmel compiler these will become 'const __flash char' and 'const __memx char*'.  All printf() functions and syslog() functions are changed so that the qualifier is used with the format parameter.
      
      From: Dimitry Kloper <dikloper@cisco.com>
      06d83c62
    • Dimitry Kloper's avatar
      The delay parameter has 'int' type while explicit int32_t is used in... · b48ca00c
      Dimitry Kloper authored
      The delay parameter has 'int' type while explicit int32_t is used in sigtimedwait() (sig_timedwait.c) This can lead to wrong argument for systems that have default int size different than int32 (namely AVR).
      b48ca00c
  8. Jan 03, 2016
  9. Jan 01, 2016