outobj: fix harmless but still incorrect use of uninitialized variable

Fix use of uninitialized variable. This most likely is just an
issue while running at debug level >= 3, but it's still wrong.

Signed-off-by: H. Peter Anvin (Intel) <hpa@zytor.com>
This commit is contained in:
H. Peter Anvin 2020-06-01 16:11:47 -07:00
parent 7002bb76a3
commit a3cbaafd52

View File

@ -833,7 +833,7 @@ static void obj_deflabel(char *name, int32_t segment,
* `first_seg'.
*/
if (!any_segs && segment == first_seg) {
int tempint; /* ignored */
int tempint = 0;
if (segment != obj_segment("__NASMDEFSEG", &tempint))
nasm_panic("strange segment conditions in OBJ driver");
}
@ -1025,7 +1025,7 @@ static void obj_out(int32_t segto, const void *data,
* segment.
*/
if (!any_segs) {
int tempint; /* ignored */
int tempint = 0;
if (segto != obj_segment("__NASMDEFSEG", &tempint))
nasm_panic("strange segment conditions in OBJ driver");
}
@ -2498,7 +2498,7 @@ static void dbgbi_linnum(const char *lnfname, int32_t lineno, int32_t segto)
* segment.
*/
if (!any_segs) {
int tempint; /* ignored */
int tempint = 0;
if (segto != obj_segment("__NASMDEFSEG", &tempint))
nasm_panic("strange segment conditions in OBJ driver");
}