You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Asar supports a number of different mapping modes. They control the address translation used by Asar during compilation (aka where in the output file Asar writes to). Historically, SNES cartridges used a number of different mappers to address data in ROM. Those mappers can be supported by using the respective mapping mode in Asar. It's possible, but not recommended, to use different mapping modes on the same ROM. Detailed explanations on each mapping mode are beyond the scope of this manual, so please check the SNES Dev Manual or other specialized resources for that.<br/>
1584
-
NOTE: Changing the mapper after having previously set it will generate warning <code>W1029</code>.<br/><br/>
1584
+
NOTE: Changing the mapper after having previously set it will generate warning <code>Wmapper_already_set</code>.<br/><br/>
Warnings are messages that Asar outputs to inform the user about potentially unintended or risky code that isn't critical and thus doesn't cause assembly to fail on its own. These messages can be useful for detecting potential problems in the code, but in some situations may be undesirable. For this reason, Asar supports a few methods of explicitly enabling or disabling certain warnings (see section <ahref="#usage">Usage</a> for details on how to configure warnings via the command line). Additionally, there are warnings which may be useful in some situations, but would be intrusive in most other situations. They are disabled by default and have to be enabled explicitly to be used. Commands that enable or disable warnings refer to them via their ID. This ID is in the format <code>WXXXX</code>, where <code>XXXX</code> is a number uniquely identifying a warning. The easiest way of finding the ID for a specific warning is to look at the console output of a patch producing it. Asar will always output the warning ID along with the respective warning.
3374
+
Warnings are messages that Asar outputs to inform the user about potentially unintended or risky code that isn't critical and thus doesn't cause assembly to fail on its own. These messages can be useful for detecting potential problems in the code, but in some situations may be undesirable. For this reason, Asar supports a few methods of explicitly enabling or disabling certain warnings (see section <ahref="#usage">Usage</a> for details on how to configure warnings via the command line). Additionally, there are warnings which may be useful in some situations, but would be intrusive in most other situations. They are disabled by default and have to be enabled explicitly to be used. Commands that enable or disable warnings refer to them via their names. The easiest way of finding the name of a specific warning is to look at the console output of a patch producing it. Asar will always output the warning name along with the respective warning.
3375
3375
<h4id="disabled-warnings">Disabled Warnings</h4>
3376
3376
This is a list of all warnings that are disabled by default and have to be enabled explicitly.<br/><br/>
<td>Thrown when opcodes are sized implicitly and Asar has to assume a size. An opcode is considered to be sized explicitly when either a length specifier is used or a simple hex constant that can be assumed to be of a specific size (that is, a hex constant with either two or four digits). Opcodes that don't support multiple sizes are always considered to be sized explicitly. Everything else is considered to be sized implicitly and will throw this warning when enabled.</td>
3385
3385
</tr>
3386
3386
<tr>
3387
-
<td><code>W1024</code></td>
3387
+
<td><code>Wcheck_memory_file</code></td>
3388
3388
<td>Only relevant for the DLL API. Thrown when a file is accessed that was either not provided as a memory file or that isn't found in memory. Mainly intended for debugging purposes and can be used to assure that files are actually read from the correct location.</td>
The <codeclass="65c816_asar">warnings push</code> command pushes the current state of enabled and disabled warnings to the stack. The <codeclass="65c816_asar">warnings pull</code> command pulls it back from the stack.
The <codeclass="65c816_asar">warnings enable</code> command enables the warning with the specified ID, the <codeclass="65c816_asar">warnings disable</code> command disables it. Warnings enabled or disabled via this command override warnings enabled or disabled via the command line (see section <ahref="#usage">Usage</a> for details). When using these commands inside shared code, it's recommended to do so in conjunction with <ahref="#warnings-push-pull">warnings {push/pull}</a> to prevent the modified settings from leaking into other files.
The <codeclass="65c816_asar">warnings enable</code> command enables the warning with the specified name, the <codeclass="65c816_asar">warnings disable</code> command disables it. Warnings enabled or disabled via this command override warnings enabled or disabled via the command line (see section <ahref="#usage">Usage</a> for details). When using these commands inside shared code, it's recommended to do so in conjunction with <ahref="#warnings-push-pull">warnings {push/pull}</a> to prevent the modified settings from leaking into other files.
0 commit comments