NO

Author Topic: Version 6.0, Release Candidate #2 available  (Read 6279 times)

Offline Pelle

  • Administrator
  • Member
  • *****
  • Posts: 2169
    • http://www.smorgasbordet.com
Version 6.0, Release Candidate #2 available
« on: May 24, 2009, 04:18:39 pm »
Pelles C version 6.0, Release Candidate #1, is now available for download:
http://www.smorgasbordet.com/pellesc/download.htm

Some changes from RC1:
  • German translation for 6.0 is now in the Setup.
  • Fixed C runtime random crash in stream functions, when a previously used file slot was assigned to a new file (after TR24731-2 changes).
  • Fixed dynamic C runtime problem with exported names (pocrt.dll, pocrt64.lib).
  • Fixed C compiler crash, when the input source file specified an infinite loop and the body of that loop was useless enough to be optimized away.
  • Fixed C compiler problem with "wild" jump (goto, continue, ...) out of a __try - __except block being lost (X64).
  • Fixed C compiler problem with missing space flag for printf family format check.
  • Fixed C compiler warning in main() about unreachable code, when exit() was used and implicit 'return 0' wasn't needed.
  • Fixed C compiler problem with float to (narrow) integer conversion and floating-point status flags, in standard C mode.
  • Fixed C compiler problem with overflow check for complex constant expression.
  • Fixed C compiler problem with stack layout for locals; added #pragma pack_stack for more control over this step.
  • Fixed C compiler problem with code generation for some cases of left/right shift as second argument to signed/unsigned divide or modulo (X86, X64).
  • Fixed browse information manager problem with unescaped single quote in SQL syntax.
  • Fixed linker problem with 'last chance' import resolver (module-definition file with unspecified "name").
  • Fixed linker problem with import name hint (minor, but incorrect).
  • Fixed library manager problem with import name hint (minor, but incorrect).
  • Fixed assembler problem with VARARG arguments and fastcall registers (X64).
  • Added C runtime functions _mm_malloc and _mm_free (X86, X64).
  • Added C runtime functions _strdup, _wcsdup, _strndup, _wcsndup, _strlwr, _wcslwr, _strupr, _wcsupr, _strrev, _wcsrev, wmemchr, wmemcmp, wmemcpy, wmemmove, wmemset (ARM, crtce.lib).
  • Added oldnamesce.lib, and moved some names from crtce.lib there (the /Go option will now be needed for some names) (ARM).
  • Added extension to the dirent extension, the d_type field (X86, X64, ARM).
  • Added a number of changes to the help file.
  • Added IDE feature to select first/last page in the source editor when using Shift+PgUp/PgDn.

Pelle
/Pelle

Offline Vortex

  • Member
  • *
  • Posts: 556
    • http://www.vortex.masmcode.com
Re: Version 6.0, Release Candidate #2 available
« Reply #1 on: May 24, 2009, 08:42:32 pm »
Thanks for this new release. Installing RC2, the version of Poasm in the command prompt appears to be 5.00.4 :

Code: [Select]
Pelles Macro Assembler, Version 5.00.4
Copyright (c) Pelle Orinius 2005-2008
« Last Edit: May 24, 2009, 08:44:21 pm by Vortex »
Code it... That's all...

Offline Robert

  • Member
  • *
  • Posts: 214
Re: Version 6.0, Release Candidate #2 available
« Reply #2 on: May 25, 2009, 11:27:12 am »
Thanks for this new release. Installing RC2, the version of Poasm in the command prompt appears to be 5.00.4 :

Code: [Select]
Pelles Macro Assembler, Version 5.00.4
Copyright (c) Pelle Orinius 2005-2008

Hi Vortex:

I just downloaded the 64 bit RC2 and poasm on the command line says

Pelles Macro Assembler, Version 6.00.1
Copyright (c) Pelle Orinius 2005-2009

Robert Wishlaw

Offline Pelle

  • Administrator
  • Member
  • *****
  • Posts: 2169
    • http://www.smorgasbordet.com
Re: Version 6.0, Release Candidate #2 available
« Reply #3 on: May 25, 2009, 03:29:49 pm »
Yes, I have version 6.00.1 in the development branch and in the version installed for testing.
/Pelle

Offline Vortex

  • Member
  • *
  • Posts: 556
    • http://www.vortex.masmcode.com
Re: Version 6.0, Release Candidate #2 available
« Reply #4 on: May 25, 2009, 07:19:07 pm »
Hello,

My apologies, it was my fault. Probably, something escaped from my attention. After reinstalling the package, everything is now fine.
Code it... That's all...