1. 05 Oct, 2011 8 commits
  2. 04 Oct, 2011 8 commits
    • Paul Borman's avatar
      pkg/syscall: add Mkfifo for linux platforms · 0b534bc9
      Paul Borman authored
      R=golang-dev, bradfitz
      CC=golang-dev
      https://golang.org/cl/5131055
      0b534bc9
    • Brad Fitzpatrick's avatar
      websocket: better error message in a test · c31f987b
      Brad Fitzpatrick authored
      R=golang-dev, dsymonds
      CC=golang-dev
      https://golang.org/cl/5185045
      c31f987b
    • Paul Borman's avatar
      time: make month/day name comparisons case insenstive · 93b8438e
      Paul Borman authored
      Fixes #2324.
      
      R=r, r
      CC=golang-dev
      https://golang.org/cl/5180044
      93b8438e
    • Russ Cox's avatar
      5g, 6g, 8g: fix loop finding bug, squash jmps · e2d326b8
      Russ Cox authored
      The loop recognizer uses the standard dominance
      frontiers but gets confused by dead code, which
      has a (not explicitly set) rpo number of 0, meaning it
      looks like the head of the function, so it dominates
      everything.  If the loop recognizer encounters dead
      code while tracking backward through the graph
      it fails to recognize where it started as a loop, and
      then the optimizer does not registerize values loaded
      inside that loop.  Fix by checking rpo against rpo2r.
      
      Separately, run a quick pass over the generated
      code to squash JMPs to JMP instructions, which
      are convenient to emit during code generation but
      difficult to read when debugging the -S output.
      A side effect of this pass is to eliminate dead code,
      so the output files may be slightly smaller and the
      optimizer may have less work to do.
      There is no semantic effect, because the linkers
      flatten JMP chains and delete dead instructions
      when laying out the final code.  Doing it here too
      just makes the -S output easier to read and more
      like what the final binary will contain.
      
      The "dead code breaks loop finding" bug is thus
      fixed twice over.  It seemed prudent to fix loopit
      separately just in case dead code ever sneaks back
      in for one reason or another.
      
      R=ken2
      CC=golang-dev
      https://golang.org/cl/5190043
      e2d326b8
    • Gustavo Niemeyer's avatar
      path/filepath: added Rel as the complement of Abs · da99a5bc
      Gustavo Niemeyer authored
      R=golang-dev, rsc, gustavo, r, borman
      CC=golang-dev
      https://golang.org/cl/4981049
      da99a5bc
    • Joe Poirier's avatar
      cgo: allow Window's specific path characters in flag directives. · aec89a6d
      Joe Poirier authored
      Example: #cgo windows LDFLAGS: -LC:\\WINDOWS\\system32
      
      R=alex.brainman, go.peter.90, golang-dev, rsc
      CC=golang-dev
      https://golang.org/cl/5154042
      aec89a6d
    • Brad Fitzpatrick's avatar
      Fix build, disabling flaky registerization test. · 2cef85f8
      Brad Fitzpatrick authored
      R=golang-dev, dsymonds
      CC=golang-dev
      https://golang.org/cl/5179045
      2cef85f8
    • Nigel Tao's avatar
      image: spin off a new color package out of the image package. · a2846e65
      Nigel Tao authored
      The spin-off renames some types. The new names are simply better:
      image.Color              -> color.Color
      image.ColorModel         -> color.Model
      image.ColorModelFunc     -> color.ModelFunc
      image.PalettedColorModel -> color.Palette
      image.RGBAColor          -> color.RGBA
      image.RGBAColorModel     -> color.RGBAModel
      image.RGBA64Color        -> color.RGBA64
      image.RGBA64ColorModel   -> color.RGBA64Model
      (similarly for NRGBAColor, GrayColorModel, etc)
      
      The image.ColorImage type stays in the image package, but is renamed:
      image.ColorImage -> image.Uniform
      
      The image.Image implementations (image.RGBA, image.RGBA64, image.NRGBA,
      image.Alpha, etc) do not change their name, and gain a nice symmetry:
      an image.RGBA is an image of color.RGBA, etc.
      
      The image.Black, image.Opaque uniform images remain unchanged (although
      their type is renamed from image.ColorImage to image.Uniform). The
      corresponding color types (color.Black, color.Opaque, etc) are new.
      
      Nothing in the image/ycbcr is renamed yet. The ycbcr.YCbCrColor and
      ycbcr.YCbCrImage types will eventually migrate to color.YCbCr and
      image.YCbCr, but that will be a separate CL.
      
      R=r, bsiegert
      CC=golang-dev
      https://golang.org/cl/5132048
      a2846e65
  3. 03 Oct, 2011 5 commits
  4. 01 Oct, 2011 3 commits
  5. 30 Sep, 2011 10 commits
  6. 29 Sep, 2011 6 commits