[PATCH 02/10] libiberty: Fix a crash in d_encoding()

Hi all, First time emailing gcc-patches, so I'm sorry if I get any of this wrong or if there's obvious errors repeated in my patches. AFAICT I should be sending each change individually rather than as one bulk patch, so I'm sorry about the spam too. All of these changes were found by fuzzing libi

[PATCH 01/10] libiberty: Fix an out of bounds read in d_expression_1()

Hi all, First time emailing gcc-patches, so I'm sorry if I get any of this wrong or if there's obvious errors repeated in my patches. AFAICT I should be sending each change individually rather than as one bulk patch, so I'm sorry about the spam too. All of these changes were found by fuzzing libi

[PATCH 03/10] libiberty: Fix a crash in d_print_comp_inner()

Hi all, First time emailing gcc-patches, so I'm sorry if I get any of this wrong or if there's obvious errors repeated in my patches. AFAICT I should be sending each change individually rather than as one bulk patch, so I'm sorry about the spam too. All of these changes were found by fuzzing libi

[PATCH 04/10] libiberty: Fix crash in ada_demangle()

Hi all, First time emailing gcc-patches, so I'm sorry if I get any of this wrong or if there's obvious errors repeated in my patches. AFAICT I should be sending each change individually rather than as one bulk patch, so I'm sorry about the spam too. All of these changes were found by fuzzing libi

[PATCH 06/10] libiberty: Correctly handle error result in dlang_parse_arrayliteral()

Hi all, First time emailing gcc-patches, so I'm sorry if I get any of this wrong or if there's obvious errors repeated in my patches. AFAICT I should be sending each change individually rather than as one bulk patch, so I'm sorry about the spam too. All of these changes were found by fuzzing libi

[PATCH 05/10] libiberty: Fix stack underflow in dlang_parse_integer()

Hi all, First time emailing gcc-patches, so I'm sorry if I get any of this wrong or if there's obvious errors repeated in my patches. AFAICT I should be sending each change individually rather than as one bulk patch, so I'm sorry about the spam too. All of these changes were found by fuzzing libi

[PATCH 08/10] libiberty: Correctly handle error result in dlang_parse_tuple()

Hi all, First time emailing gcc-patches, so I'm sorry if I get any of this wrong or if there's obvious errors repeated in my patches. AFAICT I should be sending each change individually rather than as one bulk patch, so I'm sorry about the spam too. All of these changes were found by fuzzing libi

[PATCH 07/10] libiberty: Correctly handle error result in dlang_parse_structlit()

Hi all, First time emailing gcc-patches, so I'm sorry if I get any of this wrong or if there's obvious errors repeated in my patches. AFAICT I should be sending each change individually rather than as one bulk patch, so I'm sorry about the spam too. All of these changes were found by fuzzing libi

[PATCH 09/10] libiberty: Correctly handle error result in dlang_parse_assocarray()

Hi all, First time emailing gcc-patches, so I'm sorry if I get any of this wrong or if there's obvious errors repeated in my patches. AFAICT I should be sending each change individually rather than as one bulk patch, so I'm sorry about the spam too. All of these changes were found by fuzzing libi

[PATCH 10/10] libiberty: Correct an invalid assumption

Hi all, First time emailing gcc-patches, so I'm sorry if I get any of this wrong or if there's obvious errors repeated in my patches. AFAICT I should be sending each change individually rather than as one bulk patch, so I'm sorry about the spam too. All of these changes were found by fuzzing libi

Re: [PATCH 10/10] libiberty: Correct an invalid assumption

On 14/01/2019 11:10, Iain Buclaw wrote: > Thanks, do you have a copyright assignment with the FSF? No problem, and no I don't think so. I'd assumed these patches were trivial enough to not need anything like that, but if so then what do I need to do? > Rather than checking for overflow twice, I