NASM 2.10 uses "- Ox" by default (Announce)
> Yes -O0 produces the same result :)
I believe the rationale for this was that approx. 99% of people don't want "unoptimized" (bigger) code by default. Esp. if you compare FASM and YASM have already forced such size optimization for years without any huge complaints. I think the recommended workaround (if you are the hardcore users that needs specific opcode sizes) is to use the keyword "strict" selectively.
Complete thread:
- NASM 2.10 - Rugxulo, 27.03.2012, 00:39
![Open in board view [Board]](img/board_d.gif)
![Open in mix view [Mix]](img/mix_d.gif)
- NASM 2.10 - Rugxulo, 27.03.2012, 00:42
- NASM 2.10 - marcov, 27.03.2012, 13:07
- NASM 2.10 - revised preprocessor - ecm, 20.04.2012, 04:26
- NASM 2.10 - revised preprocessor - RayeR, 02.05.2012, 22:06
- NASM 2.10 - revised preprocessor - ecm, 02.05.2012, 22:16
- NASM 2.10 - revised preprocessor - RayeR, 02.05.2012, 22:43
- NASM 2.10 - revised preprocessor - ecm, 02.05.2012, 22:48
- NASM 2.10 - revised preprocessor - RayeR, 03.05.2012, 00:04
- NASM 2.10 uses "- Ox" by default - Rugxulo, 03.05.2012, 02:25
- NASM 2.10 uses "-Ox" by default - ecm, 03.05.2012, 02:37
- NASM 2.10 uses "-Ox" by default - Rugxulo, 03.05.2012, 08:18
- NASM 2.10 uses "-Ox" by default - ecm, 03.05.2012, 23:00
- NASM 2.10.01 - Rugxulo, 16.06.2012, 00:24
- NASM 2.10 uses "-Ox" by default - ecm, 03.05.2012, 23:00
- NASM 2.10 uses "-Ox" by default - Rugxulo, 03.05.2012, 08:18
- NASM 2.10 uses "-Ox" by default - ecm, 03.05.2012, 02:37
- NASM 2.10 - revised preprocessor - ecm, 03.05.2012, 02:26
- NASM 2.10 uses "- Ox" by default - Rugxulo, 03.05.2012, 02:25
- NASM 2.10 - revised preprocessor - RayeR, 03.05.2012, 00:04
- NASM 2.10 - revised preprocessor - ecm, 02.05.2012, 22:48
- NASM 2.10 - revised preprocessor - RayeR, 02.05.2012, 22:43
- NASM 2.10 - revised preprocessor - ecm, 02.05.2012, 22:16
- NASM 2.10 - revised preprocessor - RayeR, 02.05.2012, 22:06
- NASM 2.10 - Rugxulo, 27.03.2012, 00:42
Mix view