From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oo1-xc2c.google.com (mail-oo1-xc2c.google.com [IPv6:2607:f8b0:4864:20::c2c]) by sourceware.org (Postfix) with ESMTPS id 85FE13858D33 for ; Wed, 18 Oct 2023 14:33:58 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 85FE13858D33 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 85FE13858D33 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=2607:f8b0:4864:20::c2c ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1697639640; cv=none; b=ZUp8WInww9aqourC8iBM8+CGEbKa/SLvjznyLOu0MZjVUo7oYjPnigMC9N3JcDv34m+fxUHtXZVjs6Mu9q12Co6OzJUqDo1pMf1SVZh67KhHsbxYeRuYOud2oTFnIn0T/4VYiX7wFAh31lKgBEJB3PaCaS8IuTd3iNcTzmNkOac= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1697639640; c=relaxed/simple; bh=VTkuyuRzhKGWPFH2zWxAl0FOepOys+RWVyjAx5C5gRE=; h=DKIM-Signature:MIME-Version:From:Date:Message-ID:Subject:To; b=cU6Aico18mn4t6KTMIrBbk3VWOmEP5yJ3+bq7iDgBnP1322b0idpGVrZvLYTaBvkioXGO7j9psvw3DjX7/k5B8eITtXQ2LxCv4jMz8E8s1jd57uasstrRgiy1qV8MRMOiKFZ1od3wWFL39VKAhe649CkNww/HRJSNb+k1GWmz4E= ARC-Authentication-Results: i=1; server2.sourceware.org Received: by mail-oo1-xc2c.google.com with SMTP id 006d021491bc7-5822a990ea6so146133eaf.1 for ; Wed, 18 Oct 2023 07:33:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1697639638; x=1698244438; darn=gcc.gnu.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=VTkuyuRzhKGWPFH2zWxAl0FOepOys+RWVyjAx5C5gRE=; b=Fk3pmsxlQHq98nFz/94bwVFpTMX4V3v7rtelZkDD6JNduJxDG6LS9CSnV1m0eaOuRt ZYmErAyfD9kMi2QBBj0fvKodwFXiJgVMUVbXhkjeWcimnZVWc2ZK4QL8z/0N3lSeX9Yu nPH1a9IwikaocoPnMm3Ni8Pt11EzwFvFiyYcrvuuyN1TSoEeWbzWb/iIDZorj/Ugchgn GT/Vr4k+3iq409ZNgFSaN4f6FrYj39NJjFEUYaF1vzE/27ZU3LCQ4/sIyT4ymyCXAqkx sYHa8/YZg8wcSdySFRIDMiy4qLUZ432wFHs8zmq1Rvs+a0Xd5V2i9iV2CnJFlA/SPeMD vFGg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697639638; x=1698244438; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=VTkuyuRzhKGWPFH2zWxAl0FOepOys+RWVyjAx5C5gRE=; b=HHgyVbVLncqhoDQyGsJePfG33p8EIcKb1hX5U70M9eWFS7J3YnJAImDG2FjFzgCBm8 //yr+4MbO7U9J7pZOx90fea6GaXbocVHfsqnhv9VuT8ysTv9N/+f6syWw2OaPZ1PPb5k Jw5na6UK5xeahIn3T1PkfAcrEzbu4LmDkvsxKYk8guALF4JDbOEHH3jkExlsIJc53uFr RNrx9cCo3XT1vhYB1Z+8mOpGNKVJ47vbRXki73IiXHpp/4nZxSxl+twPsVYfvSSthbxG m3EzG45ppvpb5HbENzYcy0DvtMNe112keWQ4hylYyimAiUMTH8pv+ln+zfSbFSXjPS8j zROg== X-Gm-Message-State: AOJu0Yx76aC0SlTuH0rCvcIMnRbKpdXH5gzaN8UsN4QV+qnvtb53YWfP BbuirjSgkXfmNulIEMduKw7DrtJLg0+G2AX/wqg= X-Google-Smtp-Source: AGHT+IHwX8MQNNrbwn1oeZmTwbOHFRTFBzL10pEKh1Ez3vmPhPMjoKI1KKletMxbi/up5+zK0dPFnRZmelXikPnbJ24= X-Received: by 2002:a4a:dc8f:0:b0:581:9066:49 with SMTP id g15-20020a4adc8f000000b0058190660049mr5906029oou.0.1697639637581; Wed, 18 Oct 2023 07:33:57 -0700 (PDT) MIME-Version: 1.0 From: Rishi Raj Date: Wed, 18 Oct 2023 20:03:46 +0530 Message-ID: Subject: Help needed in output relocations To: Martin Jambor , Jan Hubicka , gcc@gcc.gnu.org Content-Type: multipart/alternative; boundary="0000000000008e03050607fe8770" X-Spam-Status: No, score=-1.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: --0000000000008e03050607fe8770 Content-Type: text/plain; charset="UTF-8" Hello, I have almost completed the output of relocation entries. The only thing that remains is to output the corresponding symbols in .symtab. In my current design, I store the info about relocation entry and the symbol name. However, the problem I am facing with this approach is that many relocation entries will have the same name, so we will need a hash table with the key as symbol name and value as symbol index in symtab. It would be really helpful if you could point out the relevant docs or help me figure out how to use the hash table in GCC. Another approach is, as we have only 4-5 unique relocation symbol names. We can output just those and store their .symtab index somewhere. -- Rishi --0000000000008e03050607fe8770--