Number of commits found: 5

Upgrade AVR-GCC to GCC-3.4.4.

By the same time, combine all the patches that add support for new AVR
devices into a single patch, as they all touch the same three source
files.  In total, add support for the following AVR devices that were
not supported by the stock GCC 3.4.x:

  ATtiny13/ATtiny2313
  ATtiny25/ATtiny45/ATtiny85
  ATmega48/ATmega88/ATmega168
  AT90PWM2/AT90PWM3
  ATmega164/ATmega324/ATmega644
  ATmega325/ATmega3250/ATmega645/ATmega6450
  ATmega329/ATmega3290/ATmega649/ATmega6490
  AT90CAN128

(This is now documented in pkg-descr as well.)

Bring in some patches from the head of GCC's CVS back to the latest
released version, 3.4.3.  This mainly adds support for new AVR devices
that appeared on the market recently, and fixes a bug related to the
order of assignments for volatile uint16_t * objects (in the
assumption they might point to IO space where the order of two 8-bit
operations can be important).

Upgrade to GCC 3.4.0.

This also makes the port compile (again) under all 64-bit archs.  For
amd64, patch-ad modifies config.guess to match GCC's expectation of
x86_64.

Replace my old 16 bit IO register assignment hack by an authoritative
patch by the avr-gcc maintainers.

Bump portrevision for that.

Update to version 2002.09.01.  Included are a couple of private
patches that were floating through the avr-gcc and avr-libc
mailinglists, just for the time being until they might have been
integrated into gcc's CVS.

Portname changed from dashes in the snap date to dots so portupgrade
doesn't get confused about it.  Thanks to Brian Dean for the hint.

Number of commits found: 5

12 vulnerabilities affecting 17 ports have been reported in the past 14 days

^* - modified, not new

All vulnerabilities