[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2 04/13] contrib/elf2dmp: Conform to the error reporting pat
From: |
Peter Maydell |
Subject: |
Re: [PATCH v2 04/13] contrib/elf2dmp: Conform to the error reporting pattern |
Date: |
Wed, 6 Mar 2024 12:53:12 +0000 |
On Wed, 6 Mar 2024 at 05:01, Akihiko Odaki <akihiko.odaki@daynix.com> wrote:
>
> On 2024/03/05 22:28, Peter Maydell wrote:
> > On Tue, 5 Mar 2024 at 07:36, Akihiko Odaki <akihiko.odaki@daynix.com> wrote:
> >> @@ -206,7 +206,7 @@ static int fix_dtb(struct va_space *vs, QEMU_Elf *qe)
> >> va_space_set_dtb(vs, s->cr[3]);
> >> printf("DTB 0x%016"PRIx64" has been found from CPU #%zu"
> >> " as system task CR3\n", vs->dtb, i);
> >> - return !(va_space_resolve(vs, SharedUserData));
> >> + return !!(va_space_resolve(vs, SharedUserData));
> >
> > If the function returns bool type, we don't need the !! idiom
> > to coerce the value to bool.
>
> va_space_resolve() returns void *.
Yes, and so when we return that value, because the function
return type is 'bool' it gets correctly turned into a
true/false value. You only need !! if you want to get
a 0-or-1 value in an int return type. Or does the compiler
otherwise issue a warning here?
thanks
-- PMM
- [PATCH v2 00/13] contrib/elf2dmp: Improve robustness, Akihiko Odaki, 2024/03/05
- [PATCH v2 05/13] contrib/elf2dmp: Always check for PA resolution failure, Akihiko Odaki, 2024/03/05
- [PATCH v2 03/13] contrib/elf2dmp: Continue even contexts are lacking, Akihiko Odaki, 2024/03/05
- [PATCH v2 12/13] contrib/elf2dmp: Use GPtrArray, Akihiko Odaki, 2024/03/05
- [PATCH v2 08/13] contrib/elf2dmp: Use lduw_le_p() to read PDB, Akihiko Odaki, 2024/03/05
- [PATCH v2 13/13] contrib/elf2dmp: Clamp QEMU note to file size, Akihiko Odaki, 2024/03/05
- [PATCH v2 07/13] contrib/elf2dmp: Ensure segment fits in file, Akihiko Odaki, 2024/03/05